From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, 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-01-07 22:31:56 |
Message-ID: | 54ADB3DC.60104@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/6/15 7:33 PM, Josh Berkus wrote:
> D. Wierd name: for those doing only replication, not PITR,
> "recovery.conf" is completely baffling.
I don't disagree, but "standby.enabled" or whatever isn't any better,
for the inverse reason.
But replication and PITR are the same thing, so any name is going to
have that problem.
One way out of that would be to develop higher-level abstractions, like
pg_ctl start -m standby or something, similar to how pg_ctl promote is
an abstraction and got people away from fiddling with trigger files.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-01-07 23:14:03 | Re: INSERT ... ON CONFLICT UPDATE and RLS |
Previous Message | Alexander Korotkov | 2015-01-07 22:12:09 | Re: KNN-GiST with recheck |