| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Martín Marqués <martin(at)2ndquadrant(dot)com> |
| Subject: | Re: Add exclusive backup deprecation notes to documentation |
| Date: | 2019-03-29 12:25:07 |
| Message-ID: | CABUevEzc=pkW0coC62tjnhDeDB-1Z4MG-A_Ls0oxMuCFSuJSAw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 29, 2019 at 1:19 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Mar 29, 2019 at 6:27 AM David Steele <david(at)pgmasters(dot)net> wrote:
> > I used your suggestions with minor editing. After some reflection, I
> > agree that the inline warnings are likely to be more effective than
> > something at the end, at least for those working on a new implementation.
>
> I'm glad we could agree on something. Committed.
>
+1, thanks.
Minor nitpick:
+ backup can only be taken on a primary and does not allow concurrent
+ backups. Moreover, because it writes a backup_label file on the
+ master, it can cause the master to fail to restart automatically after
Let's be consistent in if we call it a primary or a master, at least within
the same paragraph :)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-03-29 12:28:23 | Re: [HACKERS] Block level parallel vacuum |
| Previous Message | tushar | 2019-03-29 12:24:30 | [PG 9.6]make is failing for test_decoding contrib module. |