Re: Add exclusive backup deprecation notes to documentation - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Add exclusive backup deprecation notes to documentation
Date
Msg-id 5e67c6361e64c661cd642a4229aeb8714f82625f.camel@cybertec.at
Whole thread Raw
In response to Add exclusive backup deprecation notes to documentation  (David Steele <david@pgmasters.net>)
Responses Re: Add exclusive backup deprecation notes to documentation  (David Steele <david@pgmasters.net>)
List pgsql-hackers
David Steele wrote:
> This patch attempts to document the limitations of the exclusive mode.

Thanks!

> +   <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>

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Drop type "smgr"?
Next
From: Chapman Flack
Date:
Subject: Re: Row Level Security − leakproof-ness and performance implications