Remaining Streaming Replication Open Items
in [PgSql]
|
Prev: [HACKERS] Hot Standby: Startup at shutdown checkpoint
Next: SELECT constant; takes 15x longer on 9.0?
From: Tom Lane on 6 Apr 2010 12:54 Fujii Masao <masao.fujii(a)gmail.com> writes: > On Tue, Apr 6, 2010 at 4:09 PM, Heikki Linnakangas > <heikki.linnakangas(a)enterprisedb.com> wrote: >>> � � * Fix things so that any such variables inherited from the server environment are intentionally *NOT* used for making SR connections. >> >> Drop. Besides, we have the same problem with dblink, and I don't recall >> anyone complaining. > Yep, but I don't think that dblink has the same issue because it's often > used to connect to another database on the same postgres instance, which > seems proper method. Yes, dblink is a poor precedent to cite because self-connections are a sane behavior in its case. > The problem is that walreceiver might wrongly connect > to *its* server and get stuck because no WAL records arrive for ever. > Since currently we don't allow the standby to accept the replication > connection, the problem will not happen in 9.0, and ISTM we don't need > to address it right now. So I agree to drop. Agreed, this can be put off until we support relay replication. I think it will be an issue then, however. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Heikki Linnakangas on 6 Apr 2010 13:29 Tom Lane wrote: > Heikki Linnakangas <heikki.linnakangas(a)enterprisedb.com> writes: >> I triaged the list of open items on the Streaming Replication wiki page. >> I propose that we drop the ones I've marked as Drop below, and move the >> remaining items to the main Open Items page for better visibility. > > By "drop" do you mean "move to TODO"? At least some of these issues > should be addressed in 9.1 or later. Perhaps some can really be > dropped, but it's not clear which. Umm, yes, honestly speaking I hadn't even thought about that. I've added the ones that should be addressed in the future to the TODO list. I added a new subsection for standby server and streaming replication related items: http://wiki.postgresql.org/wiki/Todo#Standby_server_mode -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Erik Rijkers" on 6 Apr 2010 14:27 On Tue, April 6, 2010 19:29, Heikki Linnakangas wrote: [...] > > I've added the ones that should be addressed in the future to the TODO > list. I added a new subsection for standby server and streaming > replication related items: > http://wiki.postgresql.org/wiki/Todo#Standby_server_mode > I reported "Assertion failure twophase.c" a few times; see: http://search.postgresql.org/search?m=1&q=Assertion+failure+twophase.c&l=&d=&s= Btw, it has now also happened once without the postbio package installed - (which was unlikely to be the cause anyway, I think). I don't see it mentioned in the TODO, but maybe it's just deemed too elusive to be assigned a todo entry. Was the issue eventually found/solved? thanks, Erik Rijkers -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 6 Apr 2010 14:58 On Tue, 2010-04-06 at 20:27 +0200, Erik Rijkers wrote: > Was the issue eventually found/solved? We think so, but the event was not conclusively traceable. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 6 Apr 2010 15:14
On Tue, 2010-04-06 at 11:06 -0400, Robert Haas wrote: > >>>> * Redefine smart shutdown in standby mode? > >>> Drop. Too big a change at this point. > >> > >> We have a working patch for this - I want to commit it. I don't think > >> it's a big change, and the current behavior is extremely pathological. > > > > Oh, ok. I didn't look at the latest patch, if it looks good to you, fine > > with me. > > I'll commit it tonight. I don't see this on hackers. Have you posted it? I'd like to see what you do before it gets committed. Thanks. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |