On Jan 9, 2010, at 7:24 AM, Keaton Adams wrote:
> Restored from last evening's backup from the master DB to make the rsync
> across the network finish sooner.
> >>
> >> Shut down the PG instance on the slave machine
> >>
> >> Ran a script that does the following:
> >>
> >> select pg_start_backup
We are still on PG 8.3.7 and I don't see pg_standby. It looks like it was
added with 8.3.8. I will put in a request to update to 8.3.9 as a part of our
next software upgrade (internal product we write) but for now I need to try to
figure out why this isn't working under 8.3.7. I did manage t
On Jan 8, 2010, at 4:50 PM, Erik Jones wrote:
>
> On Jan 8, 2010, at 9:50 AM, Keaton Adams wrote:
>
>> OK,
>>
>> So what am I doing wrong here?
>>
>> Installed PG 8.3.7 on Slave machine
>>
>> Restored from last evening's backup from the master DB to make the rsync
>> across the network fini
To clean up from a prior run.
Erik Jones wrote:
On Jan 8, 2010, at 9:50 AM, Keaton Adams wrote:
> OK,
>
> So what am I doing wrong here?
>
> Installed PG 8.3.7 on Slave machine
>
> Restored from last evening's backup from the master DB to make the rsync
> across the network finish sooner.
>
>
On Jan 8, 2010, at 9:50 AM, Keaton Adams wrote:
> OK,
>
> So what am I doing wrong here?
>
> Installed PG 8.3.7 on Slave machine
>
> Restored from last evening's backup from the master DB to make the rsync
> across the network finish sooner.
>
> Shut down the PG instance on the slave machine
OK,
So what am I doing wrong here?
Installed PG 8.3.7 on Slave machine
Restored from last evening's backup from the master DB to make the rsync across
the network finish sooner.
Shut down the PG instance on the slave machine
Ran a script that does the following:
select pg_start_backup('Maste
I did find some references to a fix of last-completed transaction time and I
looked in the postgresql-bugs archive, but I'm not having any luck confirming
that this is a problem in 8.3.7 and an upgrade to 8.3.9 would fix the issue.
postgresql 8.3.7 Fix incorrect logging of last-completed-tr
We had WAL Log shipping (warm standby) working fine under 8.1.4 but under 8.3.7
we can't get the slave to come up properly. Nothing has changed in our process
with regard to start_backup, rsync, stop_backup, bring up the warm standby
server in continuous recovery mode, but the failover DB won't
