From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Shouldn't pg_settings.enumvals be array of text? |
Date: | 2008-10-06 14:48:15 |
Message-ID: | 48EA252F.5010907@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Alvaro Herrera wrote:
> Tom Lane wrote:
>> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> Agreed, it can certainly be bettered. text[] seems to be the cleanest,
>>> but then we still have the issue with wide output in psql, no? But
>>> should we really design the view around the single use-case of psql? You
>>> can still just omit that column from the SELECT if you want...
>> Well, if we present as text[] then someone could easily use
>> array_to_string to format the column the other way. So probably
>> text[] is the right thing.
>
> Let's have it as text[] and have psql apply array_to_string() over it.
Eh, how can psql do this? You access the view with a simple SELECT *
FROM pg_settings, no?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-10-06 14:54:14 | Re: Shouldn't pg_settings.enumvals be array of text? |
Previous Message | Alvaro Herrera | 2008-10-06 14:24:04 | Re: Shouldn't pg_settings.enumvals be array of text? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-10-06 14:54:14 | Re: Shouldn't pg_settings.enumvals be array of text? |
Previous Message | Alvaro Herrera | 2008-10-06 14:24:04 | Re: Shouldn't pg_settings.enumvals be array of text? |