Thu Sep 20 14:58:10 PDT 2007
- Previous message: [Slony1-general] bug in deadlock handling?
- Next message: [Slony1-general] bug in deadlock handling?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 9/20/07, Jeff Frost <jeff at frostconsultingllc.com> wrote: > > On Thu, 20 Sep 2007, St=E9phane Schildknecht wrote: > > >> You're quite right and I think we'll start just executing the create > >> tables on all nodes independently without execute script, but the same > >> problem happens with ALTER TABLE as well, this just happened to be the > >> latest example that caused a problem. > > > > I guess no matter what the script contains, using pgpool will break the > > replication. > > Why is that? I tcpdump'd the pgpool session and did not see any extra > locks > being used. And to note, the slonik commands do not go through pgpool, > these > go straight to the master. > > I thought pgpool was supposed to be slony aware? > Really? I know that a lot of people, including myself, have _wanted_ a slony aware pgpool and for quite some time now. I'm not aware of any such code actually being written. But that's for client software anyway, certainly not the slons. Why on earth would anyone even _want_ connect a slon through pgpool? Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070920/= e3883101/attachment.htm
- Previous message: [Slony1-general] bug in deadlock handling?
- Next message: [Slony1-general] bug in deadlock handling?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list