Re: Avoid a possible overflow (src/backend/utils/sort/logtape.c) - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Avoid a possible overflow (src/backend/utils/sort/logtape.c)
Date
Msg-id CAEudQArXsT2n8_T7c2zbh72UqAK7n3VBELqHsBOx_yfA=5muJQ@mail.gmail.com
Whole thread Raw
In response to Re: Avoid a possible overflow (src/backend/utils/sort/logtape.c)  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Em ter., 29 de ago. de 2023 às 20:06, Michael Paquier <michael@paquier.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

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH v1] PQputCopyEnd never returns 0, fix the inaccurate comment
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: pg_upgrade bug: pg_upgrade successes even if the slots are defined, but they becomes unusable