Re: POC: Lock updated tuples in tuple_update() and tuple_delete()

From: Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: POC: Lock updated tuples in tuple_update() and tuple_delete()
Date: 2023-04-01 07:24:09
Message-ID: CALT9ZEFZJqcHpn_nq12XxWagn=Z2sdwLt1t=vwgbLZ2Qq9_yfg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Andres!

On Sat, 1 Apr 2023, 09:21 Andres Freund, <andres(at)anarazel(dot)de> wrote:

> Given that the in-tree state has been broken for a week, I think it
> probably
> is time to revert the commits that already went in.
>

It seems that although the patch addressing the issues is not a quick fix,
there is a big progress in it already. I propose to see it's status a week
later and if it is not ready then to revert existing. Hope there are no
other patches in the existing branch complained to suffer this.

Kind regards,
Pavel Borisov,
Supabase

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-04-01 12:49:44 Re: zstd compression for pg_dump
Previous Message Andres Freund 2023-04-01 05:21:27 Re: POC: Lock updated tuples in tuple_update() and tuple_delete()