| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype |
| Date: | 2014-02-25 09:25:17 |
| Message-ID: | CAM-w4HM2vTYipFArAow7NtrYD-GsuiBhhdpY8wh_UgNDg+wdOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25 Feb 2014 08:54, "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com> wrote:
>
>
> I hope there are no applications relying on pageinspect. It's a very
low-level tool. Or if someone has written a nice GUI around it, I'd like to
hear about it so that I can start using it :-).
>
>
>> I see more flexibility to keep them as they are now, as integers,
>> users can always tune their queries to do this post-processing with
>> to_hex for them as they've (always?) been doing.
>
>
> Agreed. With an int4, you can more easily check for a particular bit etc.
What about making it a bit() column?
What I would love to see is a function added to page inspect that takes
these two fields and returns a list of symbolic names or perhaps a tuple of
booleans.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2014-02-25 10:09:50 | Re: Custom Scan APIs (Re: Custom Plan node) |
| Previous Message | Kyotaro HORIGUCHI | 2014-02-25 09:20:18 | Re: Trigger information for auto_explain. |