Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
Date
Msg-id CAB7nPqSM_QYOZzuzDaJGhaySsCPw8hg1H=uUuWcNqmoDwdrKkQ@mail.gmail.com
Whole thread Raw
In response to Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
List pgsql-hackers
On Wed, Jan 20, 2016 at 11:41 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Joe Conway wrote:
>
>> The attached includes Bruce's change, plus I found two additional sites
>> that appear to need the same change. The xlog.c change is just a DEBUG
>> message, so not a big deal. I'm less certain if the xlogdesc.c change
>> might create some fallout.
>
> Hm, pg_xlogdump links the rmgrdesc files, so perhaps you might need to
> adjust expected test output for it.  Not really sure.

We don't depend on this output format in any tests AFAIK, at least
check-world is not complaining here and pg_xlogdump has no dedicated
tests. There may be some utility in the outside world doing some
manipulation of the string generated for this record, but that's not
worth worrying about anyway.

Patch looks fine, I have not spotted any other places that need a refresh.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Why format() adds double quote?
Next
From: Thomas Munro
Date:
Subject: Re: Proposal: "Causal reads" mode for load balancing reads without stale data