Tom Lane wrote:
> Christian Kastner <[EMAIL PROTECTED]> writes:
>> That's not what I'm seeing. The following log messages are repeated
>> every few minutes after a successful backup run:
>
>> LOG: Archivbefehl >/usr/local/bin/archive_wal.sh
>> pg_xlog/000100020009.0018C208.backup
>> 0
Christian Kastner <[EMAIL PROTECTED]> writes:
> That's not what I'm seeing. The following log messages are repeated
> every few minutes after a successful backup run:
> LOG: Archivbefehl >/usr/local/bin/archive_wal.sh
> pg_xlog/000100020009.0018C208.backup
> 000100020009.0
Tom Lane wrote:
> Wayne Conrad <[EMAIL PROTECTED]> writes:
>> On Mon, Jul 31, 2006 at 10:18:31PM +0200, Christian Kastner wrote:
>>> After the online backup script runs, all subsequent attempts to run
>>> archive_command fail because the first thing it tries to archive away is
>>> the still-existin
Wayne Conrad <[EMAIL PROTECTED]> writes:
> On Mon, Jul 31, 2006 at 10:18:31PM +0200, Christian Kastner wrote:
>> After the online backup script runs, all subsequent attempts to run
>> archive_command fail because the first thing it tries to archive away is
>> the still-existing *.backup file. This
Simon Riggs wrote:
> On Mon, 2006-07-31 at 22:18 +0200, Christian Kastner wrote:
>> Bruce Momjian wrote:
>>> What PostgreSQL version are you using? I know the *.backup file removal
>>> was added in 8.1:
>>>
>>> * Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
>>>T
On Mon, 2006-07-31 at 22:18 +0200, Christian Kastner wrote:
> Bruce Momjian wrote:
> > What PostgreSQL version are you using? I know the *.backup file removal
> > was added in 8.1:
> >
> > * Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
> >This prevents a large
On Mon, Jul 31, 2006 at 10:18:31PM +0200, Christian Kastner wrote:
> After the online backup script runs, all subsequent attempts to run
> archive_command fail because the first thing it tries to archive away is
> the still-existing *.backup file. This fails because a copy already
> exists in the
On Mon, Jul 31, 2006 at 10:18:31PM +0200, Christian Kastner wrote:
> After the online backup script runs, all subsequent attempts to run
> archive_command fail because the first thing it tries to archive away is
> the still-existing *.backup file. This fails because a copy already
> exists in the
Christian Kastner wrote:
> Bruce Momjian wrote:
> > What PostgreSQL version are you using? I know the *.backup file removal
> > was added in 8.1:
> >
> > * Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
> >This prevents a large number of "*.backup" files from exi
Bruce Momjian wrote:
> What PostgreSQL version are you using? I know the *.backup file removal
> was added in 8.1:
>
>* Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
>This prevents a large number of "*.backup" files from existing in
> "/pg_xlog".
>
> b
What PostgreSQL version are you using? I know the *.backup file removal
was added in 8.1:
* Remove old "*.backup" files when we do pg_stop_backup() (Bruce)
This prevents a large number of "*.backup" files from existing in
"/pg_xlog".
but the existance of the files sh
Hello,
I don't know why, but the .backup file created by
pg_stop_backup() in my pg_xlog never gets deleted, even though it was
successfully archived (a good copy is stored in the archive area, no
errors are raised).
The directory pg_xlog/archive_status contains a matching
.backup.d
12 matches
Mail list logo
