From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] WAL logging problem in 9.4.3? |
Date: | 2018-07-17 12:28:47 |
Message-ID: | 3c1cf991-8846-9a6f-c669-e21f8ea9a6a4@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/16/2018 08:01 PM, Michael Paquier wrote:
>
>
> I doubt as well that we'd be able to catch all the holes as well as the
> conditions where the optimization could be run safely are rather
> basically impossible to catch beforehand. I'd like to vote for getting
> rid of this optimization for COPY, this can hurt more than it is
> helpful. Per the lack of complaints, this could happen only in HEAD?
Well, we'd be getting rid of it because of a danger of data loss which
we can't otherwise mitigate. Maybe it does need to be backpatched, even
if we haven't had complaints.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2018-07-17 12:33:11 | PG 10: could not generate random cancel key |
Previous Message | Haribabu Kommi | 2018-07-17 12:15:12 | Re: Libpq support to connect to standby server as priority |