Re: pgsql: Fix potential stack overflow in incremental backup. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Fix potential stack overflow in incremental backup.
Date
Msg-id ZhdKqj5DwoOzirFv@paquier.xyz
Whole thread Raw
In response to pgsql: Fix potential stack overflow in incremental backup.  (Thomas Munro <tmunro@postgresql.org>)
Responses Re: pgsql: Fix potential stack overflow in incremental backup.
List pgsql-committers
Hi Thomas,

On Thu, Apr 11, 2024 at 01:53:24AM +0000, Thomas Munro wrote:
> Fix potential stack overflow in incremental backup.
>
> The user can set RELSEG_SIZE to a high number at compile time, so we
> can't use it to control the size of an array on the stack: it could be
> many gigabytes in size.  On closer inspection, we don't really need that
> intermediate array anyway.  Let's just write directly into the output
> array, and then perform the absolute->relative adjustment in place.
> This fixes new code from commit dc212340058.

+ * file just as if this were not an incremental backup.  The contents of the
+ * relative_block_numbers array is unspecified in this case.

Perhaps you mean s/is/are/ here?  The contents are what's not
specified.
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Fix potential stack overflow in incremental backup.
Next
From: Thomas Munro
Date:
Subject: pgsql: Fix grammar.