Re: Add exclusive backup deprecation notes to documentation

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Magnus Hagander <magnus(at)hagander(dot)net>, David Steele <david(at)pgmasters(dot)net>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Martín Marqués <martin(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Add exclusive backup deprecation notes to documentation
Date: 2019-03-01 13:14:34
Message-ID: 370124848d03833a9853316aab627d7e7291c954.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander wrote:
> Maybe have the first note say "This method is deprecated bceause it has serious
> risks (see bellow)" and then list the actual risks at the end?

Good idea. That may attract the attention of the dogs among the readers.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2019-03-01 13:34:34 Re: PostgreSQL vs SQL/XML Standards
Previous Message Christoph Berg 2019-03-01 13:12:15 Re: pgsql: Build src/port files as a library with -fPIC, and use that in li