Re: Add exclusive backup deprecation notes to documentation

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add exclusive backup deprecation notes to documentation
Date: 2019-02-28 16:08:05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

David Steele wrote:
> This patch attempts to document the limitations of the exclusive mode.


> + <para>
> + The primary issue with the exclusive method is that the
> + <filename>backup_label</filename> file is written into the data directory
> + when <function>pg_start_backup</function> is called and remains until
> + <function>pg_stop_backup</function> is called. If
> + <productname>PostgreSQL</productname> or the host terminates abnormally

There should be a comma at the end of this line.

> + then <filename>backup_label</filename> will be left in the data directory
> + and <productname>PostgreSQL</productname> will not start. A log message

You should say "*may* not start", because it will if the WAL segment is still there.

> + recommends that <filename>backup_label</filename> be removed if not
> + restoring from a backup.
> + </para>

Laurenz Albe

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2019-02-28 16:13:41 Re: Row Level Security − leakproof-ness and performance implications
Previous Message Tom Lane 2019-02-28 16:06:26 Re: Drop type "smgr"?