Re: Tighten pg_get_object_address argument checking

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Tighten pg_get_object_address argument checking
Date: 2022-09-21 10:01:59
Message-ID: CAA4eK1JtKx1+nU_dpyQ3Fh-gef2z6Raw0Uj2st4aH5DDAAag6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 20, 2022 at 11:14 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-09-21 10:08:38 Re: Add common function ReplicationOriginName.
Previous Message Yuya Watari 2022-09-21 09:43:51 Re: [PoC] Reducing planning time when tables have many partitions