Re: ON CONFLICT (and manual row locks) cause xmax of updated tupleto unnecessarily be set - Mailing list pgsql-hackers

From Andres Freund
Subject Re: ON CONFLICT (and manual row locks) cause xmax of updated tupleto unnecessarily be set
Date
Msg-id 20190725221000.i7oryd5m5z22fnir@alap3.anarazel.de
Whole thread Raw
In response to Re: ON CONFLICT (and manual row locks) cause xmax of updated tuple tounnecessarily be set  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: ON CONFLICT (and manual row locks) cause xmax of updated tuple tounnecessarily be set  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
Hi,

On 2019-07-24 17:14:39 -0700, Peter Geoghegan wrote:
> On Wed, Jul 24, 2019 at 4:24 PM Andres Freund <andres@anarazel.de> wrote:
> > but we really don't need to do any of that in this case - the only
> > locker is the current backend, after all.
> >
> > I think this isn't great, because it'll later will cause unnecessary
> > hint bit writes (although ones somewhat likely combined with setting
> > XMIN_COMMITTED), and even extra work for freezing.
> >
> > Based on a quick look this wasn't the case before the finer grained
> > tuple locking - which makes sense, there was no cases where locks would
> > need to be carried forward.
> 
> I agree that this is unfortunate. Are you planning on working on it?

Not at the moment, no. Are you planning / hoping to take a stab at it?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Thomas Munro
Date:
Subject: Re: On the stability of TAP tests for LDAP