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

From Magnus Hagander
Subject Re: Shouldn't pg_settings.enumvals be array of text?
Date
Msg-id 48EB173A.2040400@hagander.net
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:
> Greg Smith <gsmith@gregsmith.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.

Might this be the time to add an "open items for 8.4" page to the wiki?
(I'm just assuming we'll do it on the wiki and not in Bruce's mailbox
this time) I notice Greg put it on the project-specific wiki page around
GUC, but we should probably collect these things at a central location
as well.. If we want to do that, we should just ask our wiki-gurus to
create some nice templates I think :-)

//Magnus



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Transactions and temp tables
Next
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Infrastructure changes for recovery