| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Alex Shulgin <ash(at)commandprompt(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Turning recovery.conf into GUCs |
| Date: | 2015-02-19 21:33:02 |
| Message-ID: | 54E6568E.2060300@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/19/2015 12:23 PM, Peter Eisentraut wrote:
> On 1/6/15 4:22 PM, Peter Eisentraut wrote:
>> That said, there is a much simpler way to achieve that specific
>> functionality: Expose all the recovery settings as fake read-only GUC
>> variables. See attached patch for an example.
>
> The commit fest app has this as the patch of record. I don't think
> there is a real updated patch under consideration here. This item
> should probably not be in the commit fest at all.
What happened to the original patch? Regardless of what we do, keeping
recovery.conf the way it is can't be what we go forward with.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilberto Castillo | 2015-02-19 22:06:10 | FDW for Oracle |
| Previous Message | Tom Lane | 2015-02-19 21:32:12 | Re: Manipulating complex types as non-contiguous structures in-memory |