| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Rename backup_label to recovery_control |
| Date: | 2023-10-16 16:12:37 |
| Message-ID: | CA+TgmoYK3Ntsaw4LFqApBsA1dKxvWwgZkWNVSoZgAg4H8gpVBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 16, 2023 at 12:06 PM Michael Banck <mbanck(at)gmx(dot)net> wrote:
> Not sure what to do about this, but as people/companies start moving to
> 15, I am afraid we will get people complaining about this. I think
> having exclusive mode still be the default for pg_start_backup() (albeit
> deprecated) in one release and then dropping it in the next was too
> fast.
I completely agree, and I said so at the time, but got shouted down. I
think the argument that exclusive backups were breaking anything at
all was very weak. Nobody was being forced to use them, and they broke
nothing for people who didn't.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2023-10-16 16:21:41 | Re: Asymmetric partition-wise JOIN |
| Previous Message | Michael Banck | 2023-10-16 16:06:40 | Re: Rename backup_label to recovery_control |