On Fri, Oct 30, 2015 at 12:40 PM, Vladimir Borodin <r...@simply.name> wrote: > I still don’t fully understand why is it so (the problem occurs while > running only one SELECT-statement in READ COMMITED so only one snapshot is > taken), but if is expected behavior shouldn’t the documentation mention that > using READ COMMITED (which is the default) you may still get conflicts with > recovery while using replication slots?
Are you doing BEGIN / one or more SELECT statements / END? Or just a bare SELECT with no explicit transaction control? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
