--On 23. März 2011 20:37:11 + Simon Riggs wrote:
The patches are slightly different because the infrastructure isn't
all there in 8.4.
Please can you test these before I commit to 8.4.
Hi Simon,
I've searched the committers mailinglist wether this is already committed, but
either i'v
--On 23. März 2011 20:37:11 + Simon Riggs wrote:
The patches are slightly different because the infrastructure isn't
all there in 8.4.
Please can you test these before I commit to 8.4.
FYI, we have deployed patched RPMs to one of the standby servers, the one where
most of the hangs oc
Excerpts from Simon Riggs's message of mié mar 23 17:37:11 -0300 2011:
> The answer looks clear from here. What I'm stunned about is that we've
> not had a report about this before now. (You replied there had been one).
I've actually seen reports that the recovery process seems stuck but
I've nev
On Mon, Mar 21, 2011 at 4:44 PM, Bernd Helmle wrote:
> PostgreSQL is 8.4.7, WAL-Logshipping is actually using SkyTools 2.1.12 (both
> installed from PGDG rpms), running with CentOS 5.5 XEN-VM with Kernel
> 2.6.18-194.26.1.el5xen.
>
> recovery.conf on the standby installed by walmgr is
>
> restore_
PostgreSQL is 8.4.7, WAL-Logshipping is actually using SkyTools 2.1.12
(both installed from PGDG rpms), running with CentOS 5.5 XEN-VM with Kernel
2.6.18-194.26.1.el5xen.
recovery.conf on the standby installed by walmgr is
restore_command = '/usr/bin/walmgr.py
/media/pgarchive/wal-config/wal-
