Re: [COMMITTERS] pgsql: New SQL functons pg_backup_in_progress() and pg_backup_start_tim - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: [COMMITTERS] pgsql: New SQL functons pg_backup_in_progress() and pg_backup_start_tim
Date
Msg-id D960CB61B694CF459DCFB4B0128514C20808CACE@exadv11.host.magwien.gv.at
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: New SQL functons pg_backup_in_progress() and pg_backup_start_tim  (Daniel Farina <daniel@heroku.com>)
List pgsql-hackers
Daniel Farina wrote:
> After mulling over this some more, I am less on the fence about how
> unfortunate it is that Postgres cannot restart when doing an
> "exclusive" base backup: I think it is a severe anti-feature that
> should gradually be retired.

This anti-feature was introduced with
http://archives.postgresql.org/pgsql-committers/2008-04/msg00275.php
following discussions
http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php
and
http://archives.postgresql.org/pgsql-hackers/2008-03/msg01033.php

The problem (at least for me) is that without this the server will
often refuse to restart after a clean shutdown, namely when the
WAL segment containing the required checkpoint has already been
archived.

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: s/UNSPECIFIED/SIMPLE/ in foreign key code?
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Skip checkpoint on promoting from streaming replication