Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype
Date
Msg-id CAM-w4HM2vTYipFArAow7NtrYD-GsuiBhhdpY8wh_UgNDg+wdOA@mail.gmail.com
Whole thread Raw
In response to Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
<p dir="ltr"><br /> On 25 Feb 2014 08:54, "Heikki Linnakangas" <<a
href="mailto:hlinnakangas@vmware.com">hlinnakangas@vmware.com</a>>wrote:<br /> ><br /> ><br /> > I hope
thereare no applications relying on pageinspect. It's a very low-level tool. Or if someone has written a nice GUI
aroundit, I'd like to hear about it so that I can start using it :-).<br /> ><br /> ><br /> >> I see more
flexibilityto keep them as they are now, as integers,<br /> >> users can always tune their queries to do this
post-processingwith<br /> >> to_hex for them as they've (always?) been doing.<br /> ><br /> ><br /> >
Agreed.With an int4, you can more easily check for a particular bit etc.<p dir="ltr">What about making it a bit()
column?<pdir="ltr">What I would love to see is a function added to page inspect that takes these two fields and returns
alist of symbolic names or perhaps a tuple of booleans. 

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Trigger information for auto_explain.
Next
From: Kouhei Kaigai
Date:
Subject: Re: Custom Scan APIs (Re: Custom Plan node)