Re: [PATCH] Re: pg_identify_object_as_address() doesn't support pg_event_trigger oids

From: "Joel Jacobson" <joel(at)compiler(dot)org>
To: "Michael Paquier" <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: [PATCH] Re: pg_identify_object_as_address() doesn't support pg_event_trigger oids
Date: 2021-04-27 05:16:25
Message-ID: e04ff1dc-499a-48c3-8f2f-4ba9f28a71cb@www.fastmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 26, 2021, at 10:30, Michael Paquier wrote:
> On Fri, Apr 23, 2021 at 09:33:36AM +0200, Joel Jacobson wrote:
> > Also, since this is a problem also in v13 maybe this should also be
> > back-ported? I think it's a bug since both
> > pg_identify_object_as_address() and event triggers exists in v13, so
> > the function should work there as well, otherwise users would need
> > to do work-arounds for event triggers.
>
> No objections from here to do something in back-branches. We cannot
> have a test for event triggers in object_address.sql and it would be
> better to keep it in a parallel set (see 676858b for example). Could
> you however add a small test for that in event_trigger.sql? It would
> be good to check after all three functions pg_identify_object(),
> pg_identify_object_as_address() and pg_get_object_address().
> --
> Michael

Thanks for the guidance in how to test.

I've added a test at the end of event_trigger.sql,
reusing the three event triggers already in existence,
just before they are dropped.

New patch attached.

/Joel

Attachment Content-Type Size
fix_event_trigger_pg_identify_object_as_address2.patch application/octet-stream 3.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amul Sul 2021-04-27 05:20:22 Skip temporary table schema name from explain-verbose output.
Previous Message Masahiko Sawada 2021-04-27 04:27:10 Re: Replication slot stats misgivings