Re: Tighten pg_get_object_address argument checking - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Tighten pg_get_object_address argument checking
Date
Msg-id cae11966-002e-982f-0cbe-65a8f2679699@enterprisedb.com
Whole thread Raw
In response to Re: Tighten pg_get_object_address argument checking  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 21.09.22 12:01, Amit Kapila wrote:
> On Tue, Sep 20, 2022 at 11:14 PM Peter Eisentraut
> <peter.eisentraut@enterprisedb.com> wrote:
>>
>> For publication schemas (OBJECT_PUBLICATION_NAMESPACE) and user
>> mappings (OBJECT_USER_MAPPING), pg_get_object_address() checked the
>> array length of the second argument, but not of the first argument.
>> If the first argument was too long, it would just silently ignore
>> everything but the first argument.  Fix that by checking the length of
>> the first argument as well.
> 
> LGTM.

Committed, thanks for checking.




pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: confirmed_flush_lsn shows LSN of the data that has not yet been received by the logical subscriber.
Next
From: Andres Freund
Date:
Subject: Re: Mingw task for Cirrus CI