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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Subject: Re: [PATCH] Transaction traceability - txid_status(bigint)
Date: 2016-08-23 14:34:17
Message-ID: CA+Tgmoac0eS6yXN6+ck27LGu9R4QOu5v5FFQ-H4HPjecC12CgQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 23, 2016 at 10:18 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Aug 22, 2016 at 8:55 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>> Updated patch series attached. As before, 0-4 intended for commit, 5 just
>> because it'll be handy to have around for people doing wraparound related
>> testing.
>>
>> Again, thanks for taking a look.
>
> /me reviews a bit more deeply.
>
> In 0001, ...

0002 looks good, so I committed it. You forgot a function prototype
for the new SQL-callable function, though, so I added that. For me,
it generates a compiler warning if that's missing; you might want to
try to achieve a similar setup.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2016-08-23 14:36:51 Re: Logical decoding of sequence advances, part II
Previous Message Robert Haas 2016-08-23 14:18:47 Re: [PATCH] Transaction traceability - txid_status(bigint)