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
On Wed, Jun 19, 2013 at 2:02 PM, girish R G peetle
giri.anami...@gmail.comwrote:
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
On 19 June 2013 09:32, girish R G peetle giri.anami...@gmail.com wrote:
Is there a way to switch the current transaction log file in Postgres 8.0 ?
No, that was an addition to 8.2
Suggest that you send more data until the WAL file switches.
You should upgrade with some urgency.
--
Simon
On Wed, Jun 19, 2013 at 4:32 PM, Albe Laurenz laurenz.a...@wien.gv.atwrote:
girish R G peetle wrote:
@Albe
Even I was thinking to backup the transaction log files under pg_xlog
directory. But my concern is,
will it lead some kind of error or inconsistency ?
No.
During recovery,
girish R G peetle wrote:
I was wondering if I can use the modified version of your solution.
1. Convert output of pg_stop_backup to transaction log file name. (This
refers to the latest active
transaction log file)
2. If we are able to see this file under archive(WAL) directory, backup
Thanks a lot Laurenz Albe.
On Wed, Jun 19, 2013 at 6:16 PM, Albe Laurenz laurenz.a...@wien.gv.atwrote:
girish R G peetle wrote:
I was wondering if I can use the modified version of your solution.
1. Convert output of pg_stop_backup to transaction log file name. (This
refers to the
