| From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Simon Riggs *EXTERN*" <simon(at)2ndquadrant(dot)com>, "Peter Childs" <peterachilds(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: backup_label and server start |
| Date: | 2007-11-22 07:48:36 |
| Message-ID: | D960CB61B694CF459DCFB4B0128514C299CAF9@exadv11.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Wed, 2007-11-21 at 09:47 +0000, Peter Childs wrote:
>> How about this, emit a warning on shutdown and fail to shutdown until
>> the backup has finished.
>
> That would be reasonable for -m smart shutdown.
>
> We would then be treating the backup as a connection.
>
> ...but not for a fast shutdown.
>
> Any comments against?
No, that would be ok with me.
Anything that gets us out of the trap that you can shutdown
a server without any warning and then cannot restart it without
manual intervention.
What about: refuse shutdown for "smart" if a backup is in progress,
but shutdown with a loud warning for "fast".
... I still don't know what's wrong with removing backup_label
upon a clean server shutdown ...
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-11-22 07:48:42 | Re: 8.3devel slower than 8.2 under read-only load |
| Previous Message | Guillaume Smet | 2007-11-22 07:40:41 | Re: 8.3devel slower than 8.2 under read-only load |