Re: recovery.conf location
От | Robert Haas |
---|---|
Тема | Re: recovery.conf location |
Дата | |
Msg-id | AANLkTi=p5z3NP2_0HTnU_Hi+5spbFphqC7na4FS3S99=@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: recovery.conf location (Dimitri Fontaine <dfontaine@hi-media.com>) |
Ответы |
Re: recovery.conf location
|
Список | pgsql-hackers |
On Wed, Sep 29, 2010 at 3:09 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Wed, Sep 29, 2010 at 10:02 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> I think keeping the status information in a transient text file may >>> still be a good design choice. If you push it into pg_control it will >>> be impossible to modify by hand. >> >> It could be done with a trivial tool, though. > > pg_ctl standby … ? Well, no. I mean, you'd want some kind of pg_ctl utility for starting in master mode vs. slave mode, and for promoting a running slave to master. pg_ctl start -m master pg_ctl start -m slave pg_ctl promote But that's not what Tom is talking about, I don't think: you might also want a way to explicitly whack the flag in pg_control around. That would probably be along the lines of pg_resetxlog. I'm not sure how much use case there is for such a thing, but if it's needed it's certainly wouldn't be hard to write. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: