Re: Add exclusive backup deprecation notes to documentation

From: Martín Marqués <martin(at)2ndquadrant(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Add exclusive backup deprecation notes to documentation
Date: 2019-03-01 10:41:08
Message-ID: CAPdiE1zjXHVepD99kfupR38obMEAJaqaqAm4qd37Hd5-zXSGFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

El vie., 1 de mar. de 2019 a la(s) 06:21, David Steele
(david(at)pgmasters(dot)net) escribió:
>
> I added some extra language to the warning that gets emitted in the log.
> Users are more like to see that than the documentation.
>
> I also addressed a comment from another thread by adding pg_basebackup
> as .e.g. rather than or.

More awake, I gave this last patch a second read. Wording is good now.
No objections there at all.

I do think that paragraph 2 and 3 should be merged as it seems the
idea on the third is a continuation of what's in the second.

But even without that change, I believe this patch is good for commit.

Regards,

--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matsumura, Ryo 2019-03-01 10:42:34 RE: SQL statement PREPARE does not work in ECPG
Previous Message Etsuro Fujita 2019-03-01 10:26:01 Re: Oddity with parallel safety test for scan/join target in grouping_planner