Marco Colombo wrote:
I'll try that out. Maybe my ideas are so far from the truth that I'm
having a hard time in explaing them to people who actually know how
things work. I'll be back with results. Meanwhile, thanks for your time.
I think I finally got it.
Segment 34 in my pg_xlog got
Marco Colombo [EMAIL PROTECTED] writes:
Good to know, thanks. I think I'll experiment a bit with
archive_command. My point was that since I know (or better assume) that
old segments are going to stay in my pg_xlog for *days* before getting
recycled,
On what do you base that assumption? Once
Tom Lane wrote:
Marco Colombo [EMAIL PROTECTED] writes:
Good to know, thanks. I think I'll experiment a bit with
archive_command. My point was that since I know (or better assume) that
old segments are going to stay in my pg_xlog for *days* before getting
recycled,
On what do you base that
Tom Lane wrote:
No. You have to have an actual archive_command script copying the WAL
segments somewhere else when told to. An asynchronous copy of the xlog
directory will be nothing but garbage, because we recycle WAL segments
as fast as we can (ie, as soon as the archive_command claims to
Marco Colombo wrote:
Mmm, sorry I'm not sure I'm following here. Maybe I should provide some
background. In my pg_xlog directory I see five files, WAL segments, I
suppose. Only one (as I expected) is begin currently used, the others
are old (one a couple of days old).
When PG performs a switch
Hi,
The procedure you followed is for online backups. The backups are useless
unless you set archive_command in your postgresql.conf file. This command
will copy the filled transaction log to a directory where you specified in
your archive_command. The PG won't write to transaction logs unless
Richard Huxton wrote:
It calls archive_command on the just-filled one.
Good to know, thanks. I think I'll experiment a bit with
archive_command. My point was that since I know (or better assume) that
old segments are going to stay in my pg_xlog for *days* before getting
recycled, just copying
Hello,
I have a few questions on backuping a PostgreSQL server (lets say
anything 8.x.x). I've read Continuous Archiving and Point-In-Time
Recovery (PITR) in the manual I'm still missing something...well
actually I think I don't but I've been debating on this with a friend
for a while, and there's
Marco Colombo [EMAIL PROTECTED] writes:
Am I right in assuming that the following procedure is ok?
1) issue pg_start_backup();
2) copy (or tar or cpio) the data dir, w/o pg_xlog/
3) issue pg_stop_backup();
4) copy (or tar or cpio) pg_xlog/ contents.
No. You have to have an actual
On 14.05.2007 16:54, Marco Colombo wrote:
I have a few questions on backuping a PostgreSQL server (lets say
anything 8.x.x). I've read Continuous Archiving and Point-In-Time
Recovery (PITR) in the manual I'm still missing something...well
actually I think I don't but I've been debating on this
10 matches
Mail list logo
