Re: Adding REPACK [concurrently]

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net>
Subject: Re: Adding REPACK [concurrently]
Date: 2026-02-25 19:04:13
Message-ID: 97234.1772046253@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:

> On 2026-Feb-25, Antonin Houska wrote:
>
> > > Hmm, so on the apply side when reading the file, we would first reach
> > > each toast attribute value, which we know to insert directly to the
> > > toast table (keeping track of each individually toast pointer as we do
> > > so); then we reach the heap tuple itself, we [... somehow ...] interpret
> > > these external indirect toast pointers and substitute the toast pointers
> > > that we created. So we never have to construct the entire tuple, or
> > > indeed do anything else with the toasted values other than insert them
> > > into the toast table.
> >
> > Yes, that's what I mean.
>
> Makes sense. Would you be able to try and implement that?

Yes, I'll try in the following days.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-02-25 19:17:25 CLI interface to AdjustUpgrade.pm
Previous Message Masahiko Sawada 2026-02-25 19:03:08 Re: Initial COPY of Logical Replication is too slow