Re: Shouldn't pg_settings.enumvals be array of text?
От | Magnus Hagander |
---|---|
Тема | Re: Shouldn't pg_settings.enumvals be array of text? |
Дата | |
Msg-id | 48EA252F.5010907@hagander.net обсуждение исходный текст |
Ответ на | Re: Shouldn't pg_settings.enumvals be array of text? (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: Shouldn't pg_settings.enumvals be array of text?
Re: Shouldn't pg_settings.enumvals be array of text? |
Список | pgsql-hackers |
Alvaro Herrera wrote: > Tom Lane wrote: >> Magnus Hagander <magnus@hagander.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
В списке pgsql-hackers по дате отправления: