Yeah, I don't know how I produced the crash in the first place, because of course the self-replica should block all writes, and retesting it I can't get it to accept a write. Not sure how I did it in the first place.
So the bug is just that you can connect a server to itself as its own replica. Since I can't think of any good reason to do this, we should simply error out on startup if someone sets things up that way. How can we detect that we've connected streaming replication to the same server? ----- Original Message ----- > On Thu, May 17, 2012 at 10:42 PM, Ants Aasma <a...@cybertec.at> > wrote: > > On Thu, May 17, 2012 at 3:42 PM, Joshua Berkus <j...@agliodbs.com> > > wrote: > >> Even more fun: > >> > >> 1) Set up a server as a cascading replica (e.g. max_wal_senders = > >> 3, standby_mode = on ) > >> > >> 2) Connect the server to *itself* as a replica. > >> > >> 3) This will work and report success, up until you do your first > >> write. > >> > >> 4) Then ... segfault! > > > > I cannot reproduce this. > > Me, neither. > > Josh, could you show me the more detail procedure to reproduce the > problem? > > Regards, > > -- > Fujii Masao > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
