Re: Fix inappropriate uses of PG_GETARG_UINT32() - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: Fix inappropriate uses of PG_GETARG_UINT32()
Date
Msg-id 0F72983B-C1CC-4443-AC75-F3BFFA43A45B@amazon.com
Whole thread Raw
In response to Fix inappropriate uses of PG_GETARG_UINT32()  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Fix inappropriate uses of PG_GETARG_UINT32()  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On 12/1/21, 10:29 AM, "Peter Eisentraut" <peter.eisentraut@enterprisedb.com> wrote:
> The attached patch fixes this by accepting the argument using
> PG_GETARG_INT32(), doing some checks, and then casting it to unsigned
> for the rest of the code.
>
> The patch also fixes another inappropriate use in an example in the
> documentation.  These two were the only inappropriate uses I found,
> after we had fixed a few recently.

LGTM

Nathan


pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: row filtering for logical replication
Next
From: Melanie Plageman
Date:
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)