From: Antonin Houska <ah@cybertec.at>
To: Mihail Nikalayeu <mihailnikalayeu@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
    Pg Hackers <pgsql-hackers@lists.postgresql.org>,
    Robert Treat <rob@xzilla.net>
Subject: Re: Adding REPACK [concurrently]
In-reply-to: <67772.1772462341@localhost>
References: <202602251618.dpgvox64vziz@alvherre.pgsql>
 <97234.1772046253@localhost> <87648.1772217509@localhost>
 <CADzfLwWC8gk5CPTjthN873KKGWsTqOnfEx2Z_2Nr6i=V8Y70Kw@mail.gmail.com>
 <67772.1772462341@localhost>
Comments: In-reply-to Antonin Houska <ah@cybertec.at>
   message dated "Mon, 02 Mar 2026 15:39:01 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83636.1772472210.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 02 Mar 2026 18:23:30 +0100
Message-ID: <83637.1772472210@localhost>
Archived-At: 
 <https://www.postgresql.org/message-id/83637.1772472210%40localhost>
Precedence: bulk

Antonin Houska <ah@cybertec.at> wrote:

> Mihail Nikalayeu <mihailnikalayeu@gmail.com> wrote:
> > ------------
> > =

> > > attrs =3D palloc0_array(Datum, desc->natts);
> > > isnull =3D palloc0_array(bool, desc->natts);
> > =

> > It looks like there is a memory leak with those arrays.
> =

> I suppose you mean store_change(). Yes, I tried to free the individual c=
hunks
> and forgot these. The next version uses a new, per-change memory context=
.

I realize now that I forgot to reset the context at the end of the
function. I'll fix that in the next version (which will probably be posted
rather soon).

-- =

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