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
