Re: Shouldn't pg_settings.enumvals be array of text?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Shouldn't pg_settings.enumvals be array of text?
Date: 2008-10-06 14:24:04
Message-ID: 20081006142404.GC4304@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

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.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-10-06 14:48:15 Re: Shouldn't pg_settings.enumvals be array of text?
Previous Message Tom Lane 2008-10-06 14:15:11 Re: Shouldn't pg_settings.enumvals be array of text?

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2008-10-06 14:48:15 Re: Shouldn't pg_settings.enumvals be array of text?
Previous Message Tom Lane 2008-10-06 14:15:11 Re: Shouldn't pg_settings.enumvals be array of text?