Re: Fix api misuse (src/bin/pg_amcheck/pg_amcheck.c)

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix api misuse (src/bin/pg_amcheck/pg_amcheck.c)
Date: 2025-02-27 11:05:07
Message-ID: CAEudQApLYnuSAh30A1chNDxTpcDged27Kr6ZfR8_JNHCyJM1cA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em qui., 27 de fev. de 2025 às 02:08, Michael Paquier <michael(at)paquier(dot)xyz>
escreveu:

> On Wed, Feb 26, 2025 at 07:04:25PM +0530, vignesh C wrote:
> > On Tue, 18 Feb 2025 at 18:18, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
> >> Similar to commit 5b94e27 [1]
> >> The correct function when freeing memory in the frontend,
> >> using the function PQescapeIdentifier, must be
> >> PQfreemem.
> >>
> >> Trivial patch attached.
> >
> > Thanks, this change looks good to me.
>
> There's no point in leaving that unfixed in pg_amcheck, so done down
> to 14 with 48e4ae9a0707.
>
Thank you Michael.

best regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message newtglobal postgresql_contributors 2025-02-27 11:09:02 Re: Replace IN VALUES with ANY in WHERE clauses during optimization
Previous Message Andres Freund 2025-02-27 10:20:05 Re: Some read stream improvements