From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
---|---|
To: | girish R G peetle <giri(dot)anamika0(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory |
Date: | 2013-06-19 09:04:48 |
Message-ID: | CA+h6AhiGmDNyUV-GFGDZ36sPeGMpiKFkbQSr+LvwMpdJDuZVvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Jun 19, 2013 at 2:02 PM, girish R G peetle
<giri(dot)anamika0(at)gmail(dot)com>wrote:
> Hi
> The question is regrading PostgreSQL 8.0.26 version on Linux platform. I
> know that 8.0 version is no longer supported. But one of our customer is
> using this version.
> We are using File System based backup method to protect PostgreSQL server.
>
> In PostgreSQL 8.2 and above versions, I can see that latest transaction
> log will be archived when pg_stop_backup is executed.
>
> But in PostgreSQL 8.0 version this is not happening. A transaction log
> file gets archived only when it is completely filled.
> Due to this behavior, the changes made to the server during
> pg_start_backup and pg_stop_backup won't be captured in the archived
> transaction log.
>
Is there a way to switch the current transaction log file in Postgres 8.0 ?
>
> Thanks
> Girish
>
Can you try CHECKPOINT before pg_stop_backup() and see whether it meets
your requirement ?
http://www.postgresql.org/docs/8.0/static/sql-checkpoint.html
---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-06-19 09:31:03 | Re: pg_stop_backup is not archiving latest transaction log from pg_xlog directory |
Previous Message | girish R G peetle | 2013-06-19 08:32:16 | pg_stop_backup is not archiving latest transaction log from pg_xlog directory |