Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype
От | Michael Paquier |
---|---|
Тема | Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype |
Дата | |
Msg-id | CAB7nPqR9-qgWpcbQyhP7T+zj=mp-bJhdvAjQmFmkg46R9DJkLQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Dump pageinspect to 1.2: page_header with pg_lsn datatype
|
Список | pgsql-hackers |
On Tue, Feb 25, 2014 at 10:02 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > While we're messing with this, I wonder if there's any way to have > infomask and infomask2 displayed in hex format rather than plain int > without having to specify that in every query. I'm not well known for > being able to do such conversions off the top of my head ... Something like calling DirectFunctionCall1 with to_hex and return the infomask fields as text values instead of integers? This looks straight-forward. > (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 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. -- Michael
В списке pgsql-hackers по дате отправления: