Wed Apr 17 11:36:36 PDT 2013
- Previous message: [Slony1-general] replication stalls with long-running vacuum
- Next message: [Slony1-general] yum error uninstalling slony1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To close this out for the list, this did solve my issue. No replication delays were reported when the dump was told to skip the slony schema. On Tue, Apr 16, 2013 at 12:06 PM, Vick Khera <vivek at khera.org> wrote: > > On Tue, Apr 16, 2013 at 11:35 AM, Steve Singer <ssinger at ca.afilias.info>wrote: > >> Slony takes needs an exclusive lock on sl_event to create SYNC events. If >> your pg_dump includes the slony schema then you should expect replication >> to pause. A lot of people exclude the slony schema from their pg_dumps for >> this reason. >> > > Good idea. Seems contrary to the purpose of these particular backups to > even need the slony schema. Thanks for the tip! > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20130417/e17fd20a/attachment.htm
- Previous message: [Slony1-general] replication stalls with long-running vacuum
- Next message: [Slony1-general] yum error uninstalling slony1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list