On Oct 30, 2007, at 3:42 PM, Simon Riggs wrote:
On Tue, 2007-10-30 at 08:25 -0600, Brian Wipf wrote:
I'm trying to take a base backup from the standby server in archive
recovery mode. I don't believe it's possible to connect to it to
issue
pg_start_backup/pg_stop_backup.
http://www.postgre
On 30-Oct-07, at 2:42 PM, Simon Riggs wrote:
It's safest to shutdown the standby first, take a backup then crank it
up again.
It's possible to do it online in the way you suggest, but only when
running with either full_page_writes = on or when making the backup
with
rsync, or another method t
On Tue, 2007-10-30 at 08:25 -0600, Brian Wipf wrote:
> I'm trying to take a base backup from the standby server in archive
> recovery mode. I don't believe it's possible to connect to it to issue
> pg_start_backup/pg_stop_backup.
>
> http://www.postgresql.org/docs/current/interactive/warm-sta
On 29-Oct-07, at 11:06 PM, Tom Lane wrote:
Brian Wipf <[EMAIL PROTECTED]> writes:
The process I use that leads to the warnings is simple:
I use pg_controldata to determine the current checkpoint WAL location
of the standby server. I ensure I have this WAL file and all newer
WALs. I backup a
Brian Wipf <[EMAIL PROTECTED]> writes:
> The process I use that leads to the warnings is simple:
> I use pg_controldata to determine the current checkpoint WAL location
> of the standby server. I ensure I have this WAL file and all newer
> WALs. I backup all files under the standby's database
After bringing up a PG 8.2.5 database restored from a base backup
taken from a warm standby, the following warnings are logged:
...
[2007-10-26 19:21:22 MDT] LOG: archived transaction log file
"0001017C00E2"
WARNING: relation "category_click_history" page 250226 is
uninitialize
