| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(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 11:10:21 |
| Message-ID: | 1236251421.31880.154.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-03-05 at 19:52 +0900, Fujii Masao wrote:
> 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.
Why not?
> On the other hand, restore_command
> maybe can be set safely, but I'm not sure if it's really useful at this time.
Not sure changing those parameters would be a bad thing. Other
parameters can be changed, why not those?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-03-05 11:22:34 | Re: SIGHUP during recovery |
| Previous Message | Fujii Masao | 2009-03-05 10:52:23 | Re: SIGHUP during recovery |