From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SIGHUP during recovery |
Date: | 2009-03-05 10:52:23 |
Message-ID: | 3f0b79eb0903050252u3b3d49c9r97cf3eaed3de9058@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Thu, Mar 5, 2009 at 6:28 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Should we reload recovery.conf also?
I think no for now. At least the parameters which specify the recovery target
should not be changed during recovery. On the other hand, restore_command
maybe can be set safely, but I'm not sure if it's really useful at this time.
Or, upcoming HS needs such capability?
BTW, I found that backup.sgml still had the description of log_restartpoints.
Here is the patch to remove it.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
remove_log_restartpoints_doc.patch | application/octet-stream | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-03-05 11:10:21 | Re: SIGHUP during recovery |
Previous Message | Zdenek Kotala | 2009-03-05 09:48:11 | Re: building pg_dump doesn't work |