Horton
Menu

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

Euler Taveira <euler@eulerto.com>

View thread
From: "Euler Taveira" <euler@eulerto.com>
To: "Dilip Kumar" <dilipbalaut@gmail.com>, "vignesh C" <vignesh21@gmail.com>
Cc: "shveta.malik@gmail.com" <shveta.malik@gmail.com>, "Peter Smith" <smithpb2250@gmail.com>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-30T13:44:35Z
Lists: pgsql-hackers 

On Thu, Apr 30, 2026, at 4:37 AM, Dilip Kumar wrote:
>
> Yeah we may, but I feel what we have now looks more readable.
>

My suggestion is that this function should be available in a central place.
That's not the only place that could use qualified schema and relation. If you
search for get_namespace_name_or_temp you will notice that this code path is
repeated in other parts of the code too (see ruleutils.c). It would be good if
we can have a common path for it. Maybe the signature has to be
get_qualified_relname(Oid) to accommodate other cases.


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

Commits

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

  1. Use schema-qualified names in EXCEPT clause error messages.