Re: Fix dropped object handling in pg_event_trigger_ddl_commands - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Fix dropped object handling in pg_event_trigger_ddl_commands
Date
Msg-id YMNY6RGPBRCeLmFb@paquier.xyz
Whole thread Raw
In response to Re: Fix dropped object handling in pg_event_trigger_ddl_commands  (Aleksander Alekseev <aleksander@timescale.com>)
Responses Re: Fix dropped object handling in pg_event_trigger_ddl_commands
List pgsql-hackers
On Fri, Jun 11, 2021 at 11:00:40AM +0300, Aleksander Alekseev wrote:
> The last argument should be `false` then.

Hm, nope.  I think that we had better pass true as argument here.

First, this is more consistent with the identity lookup (OK, it does
not matter as we would have discarded the object after the identity
lookup anyway, but any future shuffling of this code may not be that
wise).  Second, now that I look at it, getObjectTypeDescription() can
never be NULL as we have fallback names for relations, routines and
constraints for all object types so the buffer will be filled with
some data.  Let's replace the bottom of getObjectTypeDescription()
that returns now NULL by Assert(buffer.len > 0).  This code is new as
of v14, so it is better to adjust that sooner than later.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: recovery test failures on hoverfly
Next
From: Robert Haas
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2