| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add timeline to partial WAL segments |
| Date: | 2018-12-21 06:12:43 |
| Message-ID: | 08e88c24-9996-0a7b-2475-20049c67ef33@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/20/18 10:56 PM, Robert Haas wrote:
> On Fri, Dec 14, 2018 at 6:05 PM David Steele <david(at)pgmasters(dot)net> wrote:
>> The question in my mind: is it safe to back-patch?
>
> I cannot imagine it being a good idea to stick a behavioral change
> like this into a minor release. Yeah, it lets people get out from
> under this problem a lot sooner, but it potentially breaks backup
> scripts even for people who were not suffering in the first place. I
> don't think solving this problem for the people who have it is worth
> inflicting that kind of breakage on everybody.
Fair enough -- figured I would make an argument and see what people thought.
It's easy enough to solve on my end, but I'll wait and see what naming
scheme we come up with.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-12-21 06:17:12 | Re: Change pgarch_readyXlog() to return .history files first |
| Previous Message | Tatsuro Yamada | 2018-12-21 05:51:51 | Re: Tab completion for ALTER INDEX|TABLE ALTER COLUMN SET STATISTICS |