Skip site navigation (1) Skip section navigation (2)

Re: pg_stop_backup does not complete

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-02-23 19:25:33
Message-ID: 4B83D74D020000250002F53F@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
 
> The correct resolution is to put in an archive_command that works.
 
One really should ensure that WAL files (or should I now say data?
;-) are flowing before issuing running the pg_start_backup()
function.  The documentation has always been pretty explicit about
that:
 
http://www.postgresql.org/docs/8.4/interactive/continuous-archiving.html
 
| 24.3.2. Making a Base Backup
| 
| The procedure for making a base backup is relatively simple:
| 
| 1. Ensure that WAL archiving is enabled and working.
| 
| 2. Connect to the database as a superuser, and issue the command:
| 
| SELECT pg_start_backup('label');
| ...
 
As long as the SR documentation is equally explicit on this point,
you'd have to be blatantly going against the instructions to hit
this.
 
Which makes me think that while pg_fail_backup() might actually be a
good idea, it's not really needed to solve this, so it's 9.1
material at best.
 
-Kevin

In response to

pgsql-hackers by date

Next:From: David FetterDate: 2010-02-23 19:38:58
Subject: Re: pg_stop_backup does not complete
Previous:From: Joshua D. DrakeDate: 2010-02-23 19:24:44
Subject: Re: pg_stop_backup does not complete

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group