On Thu, Dec 22, 2016 at 12:12 AM, Craig Ringer <cr...@2ndquadrant.com> wrote:
> On 22 December 2016 at 09:55, Craig Ringer <cr...@2ndquadrant.com> wrote:
>> Updated.
>> If you think it's better to just take XidGenLock again, let me know.
> Here's a further update that merges in Robert's changes from the patch
> posted upthread.

This patch contains unresolved merge conflicts.  Maybe
SetPendingTransactionIdLimit could happen in TruncateCLOG rather than
the caller.  Instead of using an LWLock, how about a spin lock?

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:

Reply via email to