Re: [PATCH] Transaction traceability - txid_status(bigint)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Date: 2016-12-22 17:26:22
Message-ID: CA+TgmoZnEEuURQZLdjos17u-P_znfW8qSYa-r9vhNrRA_HwxCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 22, 2016 at 12:12 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 22 December 2016 at 09:55, Craig Ringer <craig(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2016-12-22 17:29:15 Re: dblink get_connect_string() passes FDW option "updatable" to the connect string, connection fails.
Previous Message Robert Haas 2016-12-22 17:22:23 Re: multi-level partitions and partition-wise joins