Re: Avoid a possible overflow (src/backend/utils/sort/logtape.c)

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, David Rowley <dgrowleyml(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid a possible overflow (src/backend/utils/sort/logtape.c)
Date: 2023-08-30 10:40:10
Message-ID: CAEudQArXsT2n8_T7c2zbh72UqAK7n3VBELqHsBOx_yfA=5muJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em ter., 29 de ago. de 2023 às 20:06, Michael Paquier <michael(at)paquier(dot)xyz>
escreveu:

> On Thu, Aug 24, 2023 at 07:02:40PM -0700, Peter Geoghegan wrote:
> > FWIW I'm pretty sure that it's impossible to run into problems here in
> > practice -- the minheap is allocated by palloc(), and the high
> > watermark number of free pages is pretty small. Even still, I agree
> > with your conclusion. There is really no reason to not be consistent
> > here.
>
> Postgres 16 RC1 is now tagged, so applied down to 13.
>
Thank you, Michael.

best regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-08-30 10:57:33 pg_upgrade bug: pg_upgrade successes even if the slots are defined, but they becomes unusable
Previous Message Aleksander Alekseev 2023-08-30 10:28:53 Re: [PATCH v1] PQputCopyEnd never returns 0, fix the inaccurate comment