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

From Tom Lane
Subject Re: Shouldn't pg_settings.enumvals be array of text?
Date
Msg-id 28443.1223334135@sss.pgh.pa.us
Whole thread Raw
In response to Re: Shouldn't pg_settings.enumvals be array of text?  (Greg Smith <gsmith@gregsmith.com>)
Responses Re: Shouldn't pg_settings.enumvals be array of text?
Re: Shouldn't pg_settings.enumvals be array of text?
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reducing some DDL Locks to ShareLock
Next
From: Tom Lane
Date:
Subject: Re: Common Table Expressions applied; some issues remain