Re: Include schema-qualified names in publication error messages. - Mailing list pgsql-hackers

From vignesh C
Subject Re: Include schema-qualified names in publication error messages.
Date
Msg-id CALDaNm0YrwGNECBihB-hHOS3E8dhLFHjkPLSxOL-riY-ujGYjw@mail.gmail.com
Whole thread
In response to Re: Include schema-qualified names in publication error messages.  ("Euler Taveira" <euler@eulerto.com>)
List pgsql-hackers
On Thu, 7 May 2026 at 17:57, Euler Taveira <euler@eulerto.com> wrote:
>
> On Thu, May 7, 2026, at 3:00 AM, vignesh C wrote:
> >
> > * v5-0001-Include-schema-qualified-names-in-EXCEPT-clause-e.patch
> > * v5-0002-Include-schema-qualified-names-in-non-EXCEPT-publ.patch
>
> Regarding v5-0002:
>
>  check_publication_add_relation(PublicationRelInfo *pri)
>  {
>         Relation        targetrel = pri->relation;
> -       const char *relname;
>         const char *errormsg;
>
>         if (pri->except)
> -       {
> -               relname = get_relation_qualified_name(targetrel);
>                 errormsg = gettext_noop("cannot specify relation \"%s\" in the publication EXCEPT clause");
> -       }
>         else
> -       {
> -               relname = RelationGetRelationName(targetrel);
>                 errormsg = gettext_noop("cannot add relation \"%s\" to publication");
> -       }
>
> Why did you remove relname variable? In addition to reduce the patch size, you
> avoid increasing the number of modifications if the function
> get_relation_qualified_name is modified in the future.

I initially wanted to keep the changes aligned with the implementation
in HEAD. However, now that the patch has been committed, I agree with
retaining the variable. The attached patch includes the corresponding
changes.

Regards,
Vignesh

Attachment

pgsql-hackers by date:

Previous
From: solaimurugan vellaipandiyan
Date:
Subject: Re: Function scan FDW pushdown
Next
From: Alexander Pyhalov
Date:
Subject: Re: Function scan FDW pushdown