| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Dilip Kumar" <dilipbalaut(at)gmail(dot)com>, "vignesh C" <vignesh21(at)gmail(dot)com> |
| Cc: | "shveta(dot)malik(at)gmail(dot)com" <shveta(dot)malik(at)gmail(dot)com>, "Peter Smith" <smithpb2250(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Include schema-qualified names in publication error messages. |
| Date: | 2026-04-30 13:44:35 |
| Message-ID: | 20eff92d-bdf7-41af-850f-1e15665d6cc8@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2026-04-30 13:53:36 | Re: Include schema-qualified names in publication error messages. |
| Previous Message | Ashutosh Bapat | 2026-04-30 12:31:22 | Re: Fix DROP PROPERTY GRAPH "unsupported object class" error |