Re: Include schema-qualified names in publication error messages.

Euler Taveira <euler@eulerto.com>

From: "Euler Taveira" <euler@eulerto.com>

To: "Amit Kapila" <amit.kapila16@gmail.com>

Cc: "shveta.malik@gmail.com" <shveta.malik@gmail.com>, "vignesh C" <vignesh21@gmail.com>, "Dilip Kumar" <dilipbalaut@gmail.com>, "Peter Smith" <smithpb2250@gmail.com>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>, "shveta malik" <shvetamalik@gmail.com>

Date: 2026-05-07T12:37:17Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Use schema-qualified names in EXCEPT clause error messages.
- a49b9cfd72d8 19 (unreleased) cited

On Thu, May 7, 2026, at 9:36 AM, Amit Kapila wrote:
> On Thu, May 7, 2026 at 5:50 PM Euler Taveira <euler@eulerto.com> wrote:
>
> This suggestion sounds reasonable to me but I suggest instead moving
> this new function to rel.h as an inline function or into relcache.c as
> those are the places where we take functions with Relation as input.
> Additionally, we can name the function as
> RelationGetQualifiedRelationName().
>

LGTM.


-- 
Euler Taveira
EDB   https://www.enterprisedb.com/