Re: Support for XLogRecPtr in expand_fmt_string? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support for XLogRecPtr in expand_fmt_string?
Date
Msg-id 1342208075.23760.1.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Support for XLogRecPtr in expand_fmt_string?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Support for XLogRecPtr in expand_fmt_string?  (Bruce Momjian <bruce@momjian.us>)
Re: Support for XLogRecPtr in expand_fmt_string?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On tor, 2012-07-12 at 10:13 +0300, Heikki Linnakangas wrote:
> One idea would be to use a macro, like this:
> 
> #define XLOGRECPTR_FMT_ARGS(recptr) (uint32) ((recptr) >> 32),
> (uint32) 
> (recptr)
> 
> elog(LOG, "current WAL location is %X/%X",
> XLOGRECPTR_FMT_ARGS(RecPtr));
> 
I would rather get rid of this %X/%X notation.  I know we have all grown
to like it, but it's always been a workaround.  We're now making the
move to simplify this whole business by saying, the WAL location is an
unsigned 64-bit number -- which everyone can understand -- but then why
is it printed in some funny format?




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: initdb and fsync
Next
From: Peter Eisentraut
Date:
Subject: Re: Schema version management