Re: Shouldn't pg_settings.enumvals be array of text? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Shouldn't pg_settings.enumvals be array of text?
Date
Msg-id 20081006142404.GC4304@alvh.no-ip.org
Whole thread Raw
In response to Re: Shouldn't pg_settings.enumvals be array of text?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Shouldn't pg_settings.enumvals be array of text?
List pgsql-hackers
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.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Shouldn't pg_settings.enumvals be array of text?
Next
From: Magnus Hagander
Date:
Subject: Re: Shouldn't pg_settings.enumvals be array of text?