Re: Distinguish publication exclusions in object addresses - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Distinguish publication exclusions in object addresses
Date
Msg-id CAA4eK1L3VrOBRCfT1aJZGViK6RHqxZ4SecByFAQu_PODerEdLw@mail.gmail.com
Whole thread
In response to Re: Distinguish publication exclusions in object addresses  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Distinguish publication exclusions in object addresses
List pgsql-hackers
On Wed, Sep 16, 2026 at 12:23 PM Peter Smith <smithpb2250@gmail.com> wrote:
>
> On Wed, Sep 16, 2026 at 4:46 PM Chao Li <li.evan.chao@gmail.com> wrote:
> >
> >
> >
> > > On Sep 16, 2026, at 13:50, Amit Kapila <amit.kapila16@gmail.com> wrote:
> > >
> > > --
> > > With Regards,
> > > Amit Kapila.
> > > <v4-0001-Distinguish-publication-exclusions-in-object-addr.patch>
> >
> > V4 overall looks sold to me. Just a couple of small comments:
> >
> > 1
> > ```
> > -- No entry of either kind.  testpub_default publishes nothing.
> > SELECT pg_get_object_address('publication excluded relation',
> >                              '{public, testpub_tbl1}', '{testpub_default}');
> > ERROR:  publication relation "testpub_tbl1" in publication "testpub_default" does not exist
> > ```
> >
> > For this new test, the error message is a little surprising to me. Since the requested object type is "publication
excludedrelation", I would expect the error message to say something like: 
> > ```
> > publication excluded relation "testpub_tbl1" in publication "testpub_default" does not exist
> > ```
>
> +1 this because maybe the reported table name really *does* exist and
> is part of the publication, even though the message is saying the
> exact opposite.
>

Can you share an example of such a case?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Distinguish publication exclusions in object addresses
Next
From: Ewan Young
Date:
Subject: Re: ERROR: no relation entry for relid 3