Re: [PATCHES] Show INHERIT in \du - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: [PATCHES] Show INHERIT in \du
Date
Msg-id 37ed240d0803202045y4142191fv15231bff7c21e311@mail.gmail.com
Whole thread Raw
In response to Re: [PATCHES] Show INHERIT in \du  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Show INHERIT in \du  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 21/03/2008, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>  The code is now set up so that it can pass an entire field value
>  through gettext(), but if gettext recognizes the strings "foo" and
>  "bar" that doesn't mean it will do anything useful with "foo\nbar",
>  which is what this patch would require.
>

Ouch!

>  I suspect that to solve this in a non-kluge fashion we'd need to make
>  \du pull over the plain boolean and integer values, then build a new
>  PGresult data structure on its own.  Ugh.  (Actually, without any
>  support from libpq for building PGresults, it's hard to imagine doing
>  that in a way that wouldn't be a kluge itself.)
>
>  Or we could go back to the drawing board on what the output ought to
>  look like.
>

We can't just build the output table by hand like
describeOneTableDetails does?  Admittedly it's kludgy, but it's not an
unprecedented kludge.

pgsql-hackers by date:

Previous
From: "Brendan Jurd"
Date:
Subject: Re: [PATCHES] [GENERAL] Empty arrays with ARRAY[]
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] Show INHERIT in \du