On Fri, Apr 8, 2016 at 8:49 AM, Jesper Pedersen <jesper.peder...@redhat.com> wrote: > On 04/07/2016 02:29 AM, Michael Paquier wrote: >> So recovery is conflicting here. My guess is that this patch is >> missing some lock cleanup. >> >> With the test case attached in my case the COMMIT PREPARED record does >> not even get replayed. >> > > Should we create an entry for the open item list [0] for this, due to the > replication lag [1] ? > > CommitFest entry [2] > Original commit [3] > > Cc'ed RMT.
If there is something you think needs to be fixed that is a new issue in 9.6, then yes you should. I don't quite understand what thing is from reading this, so please make sure to describe it clearly. -- 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
