> 30 окт. 2015 г., в 16:04, Robert Haas <[email protected]> написал(а): > > On Fri, Oct 30, 2015 at 12:40 PM, Vladimir Borodin <[email protected]> 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?
I’ve tried two ways - bare SELECT in autocommit mode and BEGIN; SELECT; ROLLBACK. I first described the problem in thread on pgsql-admin@ [0], there is copy-paste from psql there, but during conversation initial description was lost. [0] http://www.postgresql.org/message-id/[email protected] > > -- > Robert Haas > EnterpriseDB: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > > > -- > Sent via pgsql-admin mailing list ([email protected]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin -- Да пребудет с вами сила… https://simply.name/ru
