| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | Tom Lane *EXTERN* <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: backup_label and server start |
| Date: | 2007-11-21 14:32:22 |
| Message-ID: | 1195655542.4246.27.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-11-21 at 15:04 +0100, Albe Laurenz wrote:
> Simon Riggs wrote:
> >> If somebody stops the postmaster while an online backup is
> >> in progress, there is no warning or nothing. Only the server
> >> will fail to restart.
> >
> > Well, it seems best not to do this. There is always a need
> > for a careful
> > procedure to manually shutdown a live server, interlocking with other
> > applications. ISTM like a manual procedure will resolve this for you.
>
> You're arguing that there *should* be a manual intervention
> if a server was shutdown while a backup was active.
Shutting down the server was a manual action, so what is wrong in a
manual action to recover from that mistake?
If the shutdown was automatic, then it needs to be properly scheduled so
automatic actions do not conflict with one another.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-11-21 14:49:51 | Re: Postgres 8.3 archive_command |
| Previous Message | Albe Laurenz | 2007-11-21 14:04:47 | Re: backup_label and server start |