Possible optimization of heap_lock_tuple() - Mailing list pgsql-hackers

From Antonin Houska
Subject Possible optimization of heap_lock_tuple()
Date
Msg-id 91564.1622012614@antos
Whole thread Raw
List pgsql-hackers
It seems that a concurrent UPDATE can restart heap_lock_tuple() even if it's
not necessary. Is the attached proposal correct and worth applying?

-- 
Antonin Houska
Web: https://www.cybertec-postgresql.com


Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Fdw batch insert error out when set batch_size > 65535
Next
From: Bharath Rupireddy
Date:
Subject: Re: Batch insert in CTAS/MatView code