Re: [PATCH] Clean up property graph error messages

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Subject: Re: [PATCH] Clean up property graph error messages
Date: 2026-05-05 02:50:09
Message-ID: 0ABA607E-665C-4E25-93EB-A21DF9616E84@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On May 5, 2026, at 03:57, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
>
> Hi,
>
> While looking at the SQL/PGQ property graph error paths, I noticed a
> few small cleanups in propgraphcmds.c.
>
> The attached patch fixes a user-visible error message from "mismatching
> properties names" to "mismatching property names”,

I think changing “properties names” to “property names” is correct.

I wonder if we can also change “mismatching” to “mismatched”, so the error message is:
```
"mismatched property names in definition of label \"%s\""
```

> and moves a
> ReleaseSysCache() call before an ERROR ereport in
> check_element_properties().
>
> The existing code should be cleaned up by
> the resource owner on the ERROR path, but the explicit ReleaseSysCache()
> placed after ereport(ERROR) was unreachable.
>

Agreed.

> The regression expected output is updated for the changed error text.
>
> [On a separate note, it might be better to change all "vertexes" to "vertices",
> haven't included that in the patch though since the other one is not exactly
> wrong?]
>
> Regards,
> Ayus
> <v1-0001-Clean-up-property-graph-error-messages.patch>

So, v1 LGTM. Only thing is that I think we can also make “mismatching” to “mismatched” in the errmsg.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-05-05 02:56:38 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Richard Guo 2026-05-05 02:06:58 Re: Wrong results from inner-unique joins caused by collation mismatch