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

Re: pg_stop_backup does not complete

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-02-24 19:31:45
Message-ID: 4B857EA1.3080504@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> You haven't posted a reproduceable bug, nor is this new to 9.0.

Yes, I have.

1) set up a failing archive_command on an idle database

2) do pg_start_backup

3) do pg_stop_backup

4) pg_stop_backup waits forever (or at least 5 minutes, which as long as
I've given it so far).

> This is about what happens in production, not your laptop. The required
> behaviour in-production is to assume that the sysadmin has configured it
> correctly and we wait for them to fix the problem. 

90% of our user base does not have a sysadmin.  Or, for that matter,
even a professional DBA.

> The previous
> complaints were from people who felt they wanted to avoid invalid
> backups.

People don't deploy PostgreSQL in production in the first place if it
has this kind of "no good option from here" failure when they first try
it.  HS/SR is for use by new users of PostgreSQL as well as the
experienced.

--Josh Berkus


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-02-24 19:33:37
Subject: Re: query cancel issues in contrib/dblink
Previous:From: Simon RiggsDate: 2010-02-24 19:24:57
Subject: Re: pg_stop_backup does not complete

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