Re: pgsql: pg_upgrade: Fix inconsistency in memory freeing

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: pg_upgrade: Fix inconsistency in memory freeing
Date: 2025-04-06 16:18:45
Message-ID: 85ea8a6689f9da14fa67d29adb20e5fddedbc122.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, 2025-04-05 at 17:24 +0900, Michael Paquier wrote:
> I am back to a laptop, and just noticed that you have applied
> f4e51eab4eb0 into the tree to take care of this issue, affecting only
> HEAD.  Why didn't you do a backpatch of this commit down to v16?
> That's down to where 2a083ab807db has been applied.

My mistake, backported through 16 now.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2025-04-06 20:12:17 pgsql: pg_upgrade: Fix memory leak in check_for_unicode_update().
Previous Message Jeff Davis 2025-04-06 16:16:47 pgsql: Fix unintentional 'NULL' string literal in pg_upgrade.