| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(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 08:54:31 |
| Message-ID: | 530C5A47.503@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/25/2014 06:52 AM, Michael Paquier wrote:
> On Tue, Feb 25, 2014 at 10:02 AM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
>> (Not that it's this patch' responsibility to do that.)
> Definitely a different patch.
>
> Don't you think that this would break existing applications?
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.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2014-02-25 08:59:18 | Re: Custom Scan APIs (Re: Custom Plan node) |
| Previous Message | Kyotaro HORIGUCHI | 2014-02-25 08:36:03 | Re: Get more from indices. |