Fujii Masao writes:
> BTW, I found that backup.sgml still had the description of log_restartpoints.
> Here is the patch to remove it.
Applied, thanks.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscri
Fujii Masao wrote:
BTW, I found that backup.sgml still had the description of log_restartpoints.
Here is the patch to remove it.
Thanks, I had put that in the Open Items list so that we remember to do
that before release.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Simon Riggs wrote:
On Thu, 2009-03-05 at 19:52 +0900, Fujii Masao wrote:
Hi,
On Thu, Mar 5, 2009 at 6:28 PM, Simon Riggs 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 Thu, 2009-03-05 at 19:52 +0900, Fujii Masao wrote:
> Hi,
>
> On Thu, Mar 5, 2009 at 6:28 PM, Simon Riggs 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
Hi,
On Thu, Mar 5, 2009 at 6:28 PM, Simon Riggs 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
On Wed, 2009-03-04 at 15:58 +0200, Heikki Linnakangas wrote:
> Fujii Masao wrote:
> > Currently, the startup process ignores SIGHUP.
> >
> > The attached patch allows the startup process to re-read config file:
> > when SIGHUP arrives, the startup process also receives the signal
> > from postmas
Fujii Masao wrote:
Currently, the startup process ignores SIGHUP.
The attached patch allows the startup process to re-read config file:
when SIGHUP arrives, the startup process also receives the signal
from postmaster and reload the settings in main redo apply loop.
Obviously, this is useful to
Hi,
Currently, the startup process ignores SIGHUP.
The attached patch allows the startup process to re-read config file:
when SIGHUP arrives, the startup process also receives the signal
from postmaster and reload the settings in main redo apply loop.
Obviously, this is useful to change the param