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

From Greg Smith
Subject Re: Shouldn't pg_settings.enumvals be array of text?
Date
Msg-id Pine.GSO.4.64.0810070143250.9638@westnet.com
Whole thread Raw
In response to Re: Shouldn't pg_settings.enumvals be array of text?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 6 Oct 2008, Tom Lane wrote:

> Fine with me, but let's be sure this doesn't slide off the radar screen.
> If we forget about it and release 8.4 with the current definition of the
> column, it'll be too late to change it.

Agreed and understood.  I hope to have some basic postgresql.conf tuning 
tools packaged by the time 8.4 is released, and everything needed to sort 
out the server-side of that is in my critical path for things that need to 
happen before November 1.  text[] is my preferred format for some other 
things I'm working on, so anything that uses that for a list instead of a 
string I have to parse is a long-term win.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


pgsql-hackers by date:

Previous
From: "Robert Haas"
Date:
Subject: Re: Common Table Expressions applied; some issues remain
Next
From: Simon Riggs
Date:
Subject: Re: Reducing some DDL Locks to ShareLock