Re: For what should pg_stop_backup wait?

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: For what should pg_stop_backup wait?
Date: 2008-08-08 14:02:30
Message-ID: 1218204150.4549.610.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, 2008-08-08 at 12:57 +0100, Simon Riggs wrote:

> > Yes, statement_timeout may help. But, I don't want to use it, because the
> > *successful* backup is canceled.
> >
> > How about checking whether the stoppoint was archived by comparing with
> > the last WAL archived. The archiver process can tell the last WAL archived.
> > Or, we can calculate it from the status file.
> I think its easier to test whether the stopxlogfilename still exists in
> pg_xlog. If not, we know it has been archived away. We can add that as
> an extra condition inside the loop.
> So thinking we should test XLogArchiveCheckDone() for both
> stopxlogfilename and history file and then stat for the stop WAL file:

This seems better.

Simon Riggs
PostgreSQL Training, Services and Support

Attachment Content-Type Size
stop_backup_wait_bug.v2.patch text/x-patch 2.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-08 14:11:19 Re: Oprofile with postgresql
Previous Message Tom Lane 2008-08-08 13:42:41 Re: patch: Add columns via CREATE OR REPLACE VIEW