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

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Shouldn't pg_settings.enumvals be array of text?
Date: 2008-10-07 05:58:16
Message-ID: Pine.GSO.4.64.0810070143250.9638@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

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(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-10-07 06:21:25 Re: Reducing some DDL Locks to ShareLock
Previous Message Robert Haas 2008-10-07 04:18:10 Re: Common Table Expressions applied; some issues remain

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2008-10-07 08:00:58 Re: Shouldn't pg_settings.enumvals be array of text?
Previous Message Joshua Drake 2008-10-06 23:17:56 Re: Fwd: Supporters of Gin index