Re: [HACKERS] WAL logging problem in 9.4.3?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(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 00:01:29
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Mon, Jul 16, 2018 at 09:41:51PM +0300, Heikki Linnakangas wrote:
> On 16 July 2018 21:38:39 EEST, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>On Thu, Jul 12, 2018 at 10:12 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
>>> Doesn't have to be a trigger, could be a CHECK constraint, datatype
>>> function, etc. Admittedly, having a datatype input function that
>>inserts to
>>> the table is worth a "huh?", but I'm feeling very confident that we
>>> catch all such cases, and some of them might even be sensible.
>>Is this sentence missing a "not"? i.e. "I'm not feeling very
> Yes, sorry.

This explains a lot :p

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?

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-07-17 00:04:34 Re: Fix error message when trying to alter statistics on included column
Previous Message Alvaro Herrera 2018-07-16 23:17:13 Re: partition pruning doesn't work with IS NULL clause in multikey range partition case