Possible optimization of heap_lock_tuple()

From: Antonin Houska <ah(at)cybertec(dot)at>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Possible optimization of heap_lock_tuple()
Date: 2021-05-26 07:03:34
Message-ID: 91564.1622012614@antos
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
heap_lock_tuple.diff text/x-diff 471 bytes

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-05-26 07:06:36 Re: Batch insert in CTAS/MatView code
Previous Message Bharath Rupireddy 2021-05-26 06:57:24 Re: Fdw batch insert error out when set batch_size > 65535