From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: exposing pg_controldata and pg_config as functions |
Date: | 2015-12-23 17:08:40 |
Message-ID: | 567AD518.7070708@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/23/2015 05:45 AM, Michael Paquier wrote:
>> Yeah, the last version of the patch dates of August, and there is
>> visibly agreement that the information of pg_controldata provided at
>> SQL level is useful while the data of pg_config is proving to be less
>> interesting for remote users. Could the patch be rebased and split as
>> suggested above?
>
> I am marking this patch as returned with feedback, there is not much activity...
I just dusted this off yesterday finally. Anyway, based on the
discussions I plan to:
1) split it into two separate patches, one for pg_config and one for
pg_controldata.
2) Change the pg_controldata to be a bunch of separate functions as
suggested by Josh Berkus rather than one SRF.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-12-23 17:37:40 | Re: Using quicksort for every external sort run |
Previous Message | Alvaro Herrera | 2015-12-23 16:55:44 | Re: BUG #13741: vacuumdb does not accept valid password |