Re: INSERT ... ON CONFLICT UPDATE and logical decoding - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: INSERT ... ON CONFLICT UPDATE and logical decoding
Date
Msg-id CAM3SWZTwHKHkic=5szTOCVRGiv3PBTvzAPW_SmgxEeK-YT+fAA@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT UPDATE and logical decoding  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Fri, Feb 20, 2015 at 3:52 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2015-02-20 15:44:12 -0800, Peter Geoghegan wrote:
>> On Thu, Feb 19, 2015 at 2:11 AM, Andres Freund <andres@2ndquadrant.com> wrote:
>> > Yes. It'd be easiest if the only the final insert/update were actually
>> > WAL logged as full actions.
>>
>> Well, that implies that we'd actually know that we'd succeed when WAL
>> logging the speculative heap tuple's insertion.
>
> I don't think it does. It'd certainly be possible to simply only emit
> the final WAL logging action once the insertion has actually
> non-speculatively succeeded.  We might decide against that for
> eefficiency or complexity reasons, but it'd be far from impossible or
> even ugly.  We could even not log the actual values for the speculative
> insertion - after all, those aren't needed if we crash halfway
> through...

I think that that would be prohibitively complex and inefficient,
though. No? I will concede that it's probably possible in principle,
but that seems like a pretty academic point.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: INSERT ... ON CONFLICT UPDATE and logical decoding
Next
From: Tomas Vondra
Date:
Subject: Re: Abbreviated keys for Numeric (was: Re: B-Tree support function number 3 (strxfrm() optimization))