Re: non-HOT update not looking at FSM for large tuple update

From: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Floris Van Nee <florisvannee(at)optiver(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: non-HOT update not looking at FSM for large tuple update
Date: 2021-03-19 18:42:08
Message-ID: CAEze2Wi2r86gWbM88nyTveKmVsKDRNeY1L+fNY3GcOX8qm+2Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 19 Mar 2021 at 19:16, John Naylor <john(dot)naylor(at)enterprisedb(dot)com> wrote:
>
> On Thu, Mar 18, 2021 at 5:30 PM Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> wrote:
> >
> > This is slightly more verbose, but I think this clarifies the
> > reasoning why we need this a bit better. Feel free to reject or adapt
> > as needed.
>
> I like this in general, but still has some rough edges. I've made another attempt in v5 incorporating your suggestions. Let me know what you think.

That is indeed better.

I believe this is ready, so I've marked it as RFC in the commitfest application.

With regards,

Matthias van de Meent.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-03-19 18:52:47 Replication slot stats misgivings
Previous Message Jacob Champion 2021-03-19 18:37:05 Re: Proposal: Save user's original authenticated identity for logging