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

From Amit Kapila
Subject Re: Tighten pg_get_object_address argument checking
Date
Msg-id CAA4eK1JtKx1+nU_dpyQ3Fh-gef2z6Raw0Uj2st4aH5DDAAag6w@mail.gmail.com
Whole thread Raw
In response to Tighten pg_get_object_address argument checking  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Tighten pg_get_object_address argument checking
List pgsql-hackers
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.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Yuya Watari
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Amit Kapila
Date:
Subject: Re: Add common function ReplicationOriginName.