| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery.conf location |
| Date: | 2010-09-27 06:52:00 |
| Message-ID: | AANLkTinFyGrVk3K3s0xEmORXzNCHrHkim+hoQsWFfZVF@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 27, 2010 at 10:55 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Again, I think the real question is how to handle values that need to
> be maintained PER SLAVE from values of which there is only one copy.
Yep. One idea is to support something like "pg_ctl standby" and "pg_ctl pitr".
If we do so, we would be able to get rid of standby_mode from recovery.conf,
and move the others to postgresql.conf or elsewhere.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marios Vodas | 2010-09-27 06:52:31 | Re: forming tuple as an attribute inside another tuple in c function |
| Previous Message | SAKAMOTO Masahiko | 2010-09-27 06:50:34 | Re: patch: SQL/MED(FDW) DDL |