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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
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-06 23:02:15
Message-ID: 28443.1223334135@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> When I was looking at this code for the first time recently I thought the
> same thing Tom did here--that this was kind of odd and it should give a
> text array back instead. I would even volunteer to take a stab at writing
> that change myself just to get some more practice with this section of
> code, should be able to squeeze that in over the next month.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-07 00:39:15 Re: Common Table Expressions applied; some issues remain
Previous Message Tom Lane 2008-10-06 22:57:35 Re: Reducing some DDL Locks to ShareLock

Browse pgsql-www by date

  From Date Subject
Next Message Joshua Drake 2008-10-06 23:17:56 Re: Fwd: Supporters of Gin index
Previous Message Josh Berkus 2008-10-06 23:00:01 Re: Fwd: Supporters of Gin index