| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stop_backup does not complete |
| Date: | 2010-02-23 20:14:58 |
| Message-ID: | 603c8f071002231214s63e2d918m4d1d9406765e5a88@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 23, 2010 at 3:09 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On Tue, 2010-02-23 at 14:49 -0500, Robert Haas wrote:
>
>> > If I issue a shutdown, PostgreSQL should do whatever it needs to do to
>> > shutdown; including issuing a pg_stop_backup.
>>
>> Maybe. But for sure, if it doesn't, and instead tells the user to
>> issue pg_stop_backup(), then pg_stop_backup() had better WORK when the
>> user tries to execute it.
>
> Right.
>
>> I gather that the problem is that it has to
>> finish all that outstanding archiving before shutting down, in which
>> case Kevin's suggestion of having a command to abort the backup seems
>> reasonable. I might call it pg_abort_backup() rather than
>> pg_fail_backup(), but...
>>
>
> But...?
But it seems like a good idea other than that.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-02-23 21:03:13 | Re: phypot - Pygmy Hippotause ? |
| Previous Message | Joshua D. Drake | 2010-02-23 20:09:06 | Re: pg_stop_backup does not complete |