From: Andy Shellam <andy.shellam-lists@mailnetwork.co.uk>
To: pgsql-admin@postgresql.org
Subject: Re: Why so long between archive calls?
Date: Tue, 29 Aug 2006 17:19:25 +0100
Message-ID: <44F4690D.2010503@mailnetwork.co.uk> (raw)
In-Reply-To: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com>
References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com>
Chris,
I take it you've checked that the archive_command is actually succeeding
(check the postgresql log file.)
Perhaps try running it manually with an early log file as the PostgreSQL
user account?
When you say you're 500 files behind, how old is the earliest log?
Andy.
Chris Hoover wrote:
> I am working on getting my development system working with archive
> logging so I can use the pitr features of Postgres. However, I am
> finding that the actual archiving is not keeping up with the
> generation of the logs. I am now over 500 wal archive files behind
> (8+ GB).
>
> What controls how often the archive_command is called?
>
> The actual running of my archive script is taking 1-2 seconds, so I'm
> not sure why we are so far behind.
>
> Thanks for any advise,
>
> Chris
>
> PG 8.1.3
> RH AS 4
> !DSPAM:37,44f45f03143293039237985!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: andy.shellam-lists@mailnetwork.co.uk
Subject: Re: Why so long between archive calls?
In-Reply-To: <44F4690D.2010503@mailnetwork.co.uk>
References: <1d219a6f0608290835u6647a8e1g437dfd4cedb81658@mail.gmail.com> <44F4690D.2010503@mailnetwork.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox