Re: pg_stop_backup does not complete

Joshua D. Drake <jd@commandprompt.com>

From: "Joshua D. Drake" <jd@commandprompt.com>

To: Simon Riggs <simon@2ndQuadrant.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Josh Berkus <josh@agliodbs.com>, Greg Smith <greg@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2010-02-25T00:18:28Z

Lists: pgsql-hackers

On Wed, 2010-02-24 at 23:57 +0000, Simon Riggs wrote:
>  
> > * emit a NOTICE as soon as pg_stop_backup's actual work is done and
> > it's starting to wait for the archiver (or maybe after it's waited
> > for a few seconds, but much less than the present 60).
> 
> Pointless really. Nobody runs backups in production by typing
> pg_stop_backup() except in a demo. Nobody will see this. 

This is not true. It is not uncommon for a pitr setup to get out of sync
for any number of production reasons. It is one of the reasons that
PITRTools supports executing a pg_stop_backup.

Joshua D. Drake



-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.