public inbox for [email protected]
help / color / mirror / Atom feed[PATCH] Clean up property graph error messages
9+ messages / 4 participants
[nested] [flat]
* [PATCH] Clean up property graph error messages
@ 2026-05-04 19:57 Ayush Tiwari <[email protected]>
2026-05-05 02:50 ` Re: [PATCH] Clean up property graph error messages Chao Li <[email protected]>
2026-05-05 07:43 ` Re: [PATCH] Clean up property graph error messages Peter Eisentraut <[email protected]>
2026-05-07 08:45 ` Re: [PATCH] Clean up property graph error messages Peter Eisentraut <[email protected]>
0 siblings, 3 replies; 9+ messages in thread
From: Ayush Tiwari @ 2026-05-04 19:57 UTC (permalink / raw)
To: pgsql-hackers; Peter Eisentraut <[email protected]>; Ashutosh Bapat <[email protected]>
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", 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.
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
Attachments:
[application/octet-stream] v1-0001-Clean-up-property-graph-error-messages.patch (4.2K, 3-v1-0001-Clean-up-property-graph-error-messages.patch)
download | inline diff:
From 4c5aca2d5e754911969831a658d511fa53bdfe03 Mon Sep 17 00:00:00 2001
From: Ayush Tiwari <[email protected]>
Date: Tue, 5 May 2026 01:13:18 +0530
Subject: [PATCH v1] Clean up property graph error messages
check_element_properties() saved a ReleaseSysCache() call until after
ereport(ERROR), making the explicit release unreachable. Copy the
catalog fields needed for the error message and release the syscache
entry before building and reporting the error.
Also fix the wording of a property graph label consistency error from
"mismatching properties names" to "mismatching property names", and
update the matching expected output.
---
src/backend/commands/propgraphcmds.c | 14 +++++++++-----
.../regress/expected/create_property_graph.out | 4 ++--
2 files changed, 11 insertions(+), 7 deletions(-)
diff --git a/src/backend/commands/propgraphcmds.c b/src/backend/commands/propgraphcmds.c
index 6d509fccf46..7784dd0f5c5 100644
--- a/src/backend/commands/propgraphcmds.c
+++ b/src/backend/commands/propgraphcmds.c
@@ -1113,6 +1113,8 @@ check_element_properties(Oid peoid)
HeapTuple tuple3;
Form_pg_propgraph_element elform;
List *dpcontext;
+ char *element_name;
+ Oid element_relid;
char *dpa,
*dpb;
@@ -1120,7 +1122,11 @@ check_element_properties(Oid peoid)
if (!tuple3)
elog(ERROR, "cache lookup failed for property graph element %u", peoid);
elform = (Form_pg_propgraph_element) GETSTRUCT(tuple3);
- dpcontext = deparse_context_for(get_rel_name(elform->pgerelid), elform->pgerelid);
+ element_name = pstrdup(NameStr(elform->pgealias));
+ element_relid = elform->pgerelid;
+ ReleaseSysCache(tuple3);
+
+ dpcontext = deparse_context_for(get_rel_name(element_relid), element_relid);
dpa = deparse_expression(na, dpcontext, false, false);
dpb = deparse_expression(nb, dpcontext, false, false);
@@ -1141,10 +1147,8 @@ check_element_properties(Oid peoid)
ereport(ERROR,
errcode(ERRCODE_SYNTAX_ERROR),
errmsg("element \"%s\" property \"%s\" expression mismatch: %s vs. %s",
- NameStr(elform->pgealias), get_propgraph_property_name(propoid), dpa, dpb),
+ element_name, get_propgraph_property_name(propoid), dpa, dpb),
errdetail("In a property graph element, a property of the same name has to have the same expression in each label."));
-
- ReleaseSysCache(tuple3);
}
break;
@@ -1266,7 +1270,7 @@ check_element_label_properties(Oid ellabeloid)
if (diff1 || diff2)
ereport(ERROR,
errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
- errmsg("mismatching properties names in definition of label \"%s\"", get_propgraph_label_name(labelid)));
+ errmsg("mismatching property names in definition of label \"%s\"", get_propgraph_label_name(labelid)));
}
/*
diff --git a/src/test/regress/expected/create_property_graph.out b/src/test/regress/expected/create_property_graph.out
index bc9a596ec89..bfa6712b365 100644
--- a/src/test/regress/expected/create_property_graph.out
+++ b/src/test/regress/expected/create_property_graph.out
@@ -210,11 +210,11 @@ CREATE PROPERTY GRAPH gx
t1 KEY (a) LABEL l1 PROPERTIES (a, b),
t2 KEY (i) LABEL l1 PROPERTIES (i AS a, j AS j) -- mismatching property names on label
);
-ERROR: mismatching properties names in definition of label "l1"
+ERROR: mismatching property names in definition of label "l1"
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS yy, b AS zz); -- mismatching number of properties on label
ERROR: mismatching number of properties in definition of label "t3l1"
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS zz); -- mismatching property names on label
-ERROR: mismatching properties names in definition of label "t3l1"
+ERROR: mismatching property names in definition of label "t3l1"
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x); -- mismatching number of properties on label
ERROR: mismatching number of properties in definition of label "t3l1"
ALTER PROPERTY GRAPH g1 OWNER TO regress_graph_user1;
--
2.34.1
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
@ 2026-05-05 02:50 ` Chao Li <[email protected]>
2026-05-06 06:23 ` Re: [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2 siblings, 1 reply; 9+ messages in thread
From: Chao Li @ 2026-05-05 02:50 UTC (permalink / raw)
To: Ayush Tiwari <[email protected]>; +Cc: pgsql-hackers; Peter Eisentraut <[email protected]>; Ashutosh Bapat <[email protected]>
> On May 5, 2026, at 03:57, Ayush Tiwari <[email protected]> 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/
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-05 02:50 ` Re: [PATCH] Clean up property graph error messages Chao Li <[email protected]>
@ 2026-05-06 06:23 ` Ayush Tiwari <[email protected]>
2026-05-06 06:45 ` Re: [PATCH] Clean up property graph error messages Chao Li <[email protected]>
2026-05-07 08:46 ` Re: [PATCH] Clean up property graph error messages Peter Eisentraut <[email protected]>
0 siblings, 2 replies; 9+ messages in thread
From: Ayush Tiwari @ 2026-05-06 06:23 UTC (permalink / raw)
To: Chao Li <[email protected]>; +Cc: pgsql-hackers; Peter Eisentraut <[email protected]>; Ashutosh Bapat <[email protected]>
Hi,
On Tue, 5 May 2026 at 08:20, Chao Li <[email protected]> wrote:
>
> So, v1 LGTM. Only thing is that I think we can also make “mismatching” to
> “mismatched” in the errmsg.
>
>
I agree that "mismatched property names" reads better, so I have updated
that in v2. I did not include the vertexes/vertices change here, since
Peter has already fixed that separately.
Regards,
Ayush
Attachments:
[application/octet-stream] v2-0001-Clean-up-property-graph-error-messages.patch (5.6K, 3-v2-0001-Clean-up-property-graph-error-messages.patch)
download | inline diff:
From 5a28c695ec9218d53a0f9b913bc9d31067104d8c Mon Sep 17 00:00:00 2001
From: Ayush Tiwari <[email protected]>
Date: Wed, 6 May 2026 06:07:12 +0000
Subject: [PATCH v2] Clean up property graph error messages
Fix a typo in the error message for mismatched property names in
property graph labels.
Also move an unreachable ReleaseSysCache() before ereport(ERROR) in
check_element_properties(), copying the element alias and relation OID first
so the error path does not reference the released syscache tuple.
---
src/backend/commands/propgraphcmds.c | 14 +++++++++-----
.../regress/expected/create_property_graph.out | 8 ++++----
src/test/regress/sql/create_property_graph.sql | 4 ++--
3 files changed, 15 insertions(+), 11 deletions(-)
diff --git a/src/backend/commands/propgraphcmds.c b/src/backend/commands/propgraphcmds.c
index 48284b84db9..6a35ba698ee 100644
--- a/src/backend/commands/propgraphcmds.c
+++ b/src/backend/commands/propgraphcmds.c
@@ -1113,6 +1113,8 @@ check_element_properties(Oid peoid)
HeapTuple tuple3;
Form_pg_propgraph_element elform;
List *dpcontext;
+ char *element_name;
+ Oid element_relid;
char *dpa,
*dpb;
@@ -1120,7 +1122,11 @@ check_element_properties(Oid peoid)
if (!tuple3)
elog(ERROR, "cache lookup failed for property graph element %u", peoid);
elform = (Form_pg_propgraph_element) GETSTRUCT(tuple3);
- dpcontext = deparse_context_for(get_rel_name(elform->pgerelid), elform->pgerelid);
+ element_name = pstrdup(NameStr(elform->pgealias));
+ element_relid = elform->pgerelid;
+ ReleaseSysCache(tuple3);
+
+ dpcontext = deparse_context_for(get_rel_name(element_relid), element_relid);
dpa = deparse_expression(na, dpcontext, false, false);
dpb = deparse_expression(nb, dpcontext, false, false);
@@ -1141,10 +1147,8 @@ check_element_properties(Oid peoid)
ereport(ERROR,
errcode(ERRCODE_SYNTAX_ERROR),
errmsg("element \"%s\" property \"%s\" expression mismatch: %s vs. %s",
- NameStr(elform->pgealias), get_propgraph_property_name(propoid), dpa, dpb),
+ element_name, get_propgraph_property_name(propoid), dpa, dpb),
errdetail("In a property graph element, a property of the same name has to have the same expression in each label."));
-
- ReleaseSysCache(tuple3);
}
break;
@@ -1266,7 +1270,7 @@ check_element_label_properties(Oid ellabeloid)
if (diff1 || diff2)
ereport(ERROR,
errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
- errmsg("mismatching properties names in definition of label \"%s\"", get_propgraph_label_name(labelid)));
+ errmsg("mismatched property names in definition of label \"%s\"", get_propgraph_label_name(labelid)));
}
/*
diff --git a/src/test/regress/expected/create_property_graph.out b/src/test/regress/expected/create_property_graph.out
index 4fc4759f18e..ebb5f70787b 100644
--- a/src/test/regress/expected/create_property_graph.out
+++ b/src/test/regress/expected/create_property_graph.out
@@ -208,13 +208,13 @@ ERROR: mismatching number of properties in definition of label "l1"
CREATE PROPERTY GRAPH gx
VERTEX TABLES (
t1 KEY (a) LABEL l1 PROPERTIES (a, b),
- t2 KEY (i) LABEL l1 PROPERTIES (i AS a, j AS j) -- mismatching property names on label
+ t2 KEY (i) LABEL l1 PROPERTIES (i AS a, j AS j) -- mismatched property names on label
);
-ERROR: mismatching properties names in definition of label "l1"
+ERROR: mismatched property names in definition of label "l1"
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS yy, b AS zz); -- mismatching number of properties on label
ERROR: mismatching number of properties in definition of label "t3l1"
-ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS zz); -- mismatching property names on label
-ERROR: mismatching properties names in definition of label "t3l1"
+ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS zz); -- mismatched property names on label
+ERROR: mismatched property names in definition of label "t3l1"
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x); -- mismatching number of properties on label
ERROR: mismatching number of properties in definition of label "t3l1"
ALTER PROPERTY GRAPH g1 OWNER TO regress_graph_user1;
diff --git a/src/test/regress/sql/create_property_graph.sql b/src/test/regress/sql/create_property_graph.sql
index 241f93df302..d1f93fe94a8 100644
--- a/src/test/regress/sql/create_property_graph.sql
+++ b/src/test/regress/sql/create_property_graph.sql
@@ -163,10 +163,10 @@ CREATE PROPERTY GRAPH gx
CREATE PROPERTY GRAPH gx
VERTEX TABLES (
t1 KEY (a) LABEL l1 PROPERTIES (a, b),
- t2 KEY (i) LABEL l1 PROPERTIES (i AS a, j AS j) -- mismatching property names on label
+ t2 KEY (i) LABEL l1 PROPERTIES (i AS a, j AS j) -- mismatched property names on label
);
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS yy, b AS zz); -- mismatching number of properties on label
-ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS zz); -- mismatching property names on label
+ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x, b AS zz); -- mismatched property names on label
ALTER PROPERTY GRAPH g4 ALTER VERTEX TABLE t1 ADD LABEL t3l1 PROPERTIES (a AS x); -- mismatching number of properties on label
ALTER PROPERTY GRAPH g1 OWNER TO regress_graph_user1;
--
2.43.0
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-05 02:50 ` Re: [PATCH] Clean up property graph error messages Chao Li <[email protected]>
2026-05-06 06:23 ` Re: [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
@ 2026-05-06 06:45 ` Chao Li <[email protected]>
1 sibling, 0 replies; 9+ messages in thread
From: Chao Li @ 2026-05-06 06:45 UTC (permalink / raw)
To: Ayush Tiwari <[email protected]>; +Cc: pgsql-hackers; Peter Eisentraut <[email protected]>; Ashutosh Bapat <[email protected]>
> On May 6, 2026, at 14:23, Ayush Tiwari <[email protected]> wrote:
>
> Hi,
>
>
> On Tue, 5 May 2026 at 08:20, Chao Li <[email protected]> wrote:
>
> So, v1 LGTM. Only thing is that I think we can also make “mismatching” to “mismatched” in the errmsg.
>
> I agree that "mismatched property names" reads better, so I have updated
> that in v2. I did not include the vertexes/vertices change here, since
> Peter has already fixed that separately.
>
> Regards,
> Ayush
> <v2-0001-Clean-up-property-graph-error-messages.patch>
V2 LGTM.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-05 02:50 ` Re: [PATCH] Clean up property graph error messages Chao Li <[email protected]>
2026-05-06 06:23 ` Re: [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
@ 2026-05-07 08:46 ` Peter Eisentraut <[email protected]>
1 sibling, 0 replies; 9+ messages in thread
From: Peter Eisentraut @ 2026-05-07 08:46 UTC (permalink / raw)
To: Ayush Tiwari <[email protected]>; Chao Li <[email protected]>; +Cc: pgsql-hackers; Ashutosh Bapat <[email protected]>
On 06.05.26 08:23, Ayush Tiwari wrote:
> On Tue, 5 May 2026 at 08:20, Chao Li <[email protected]
> <mailto:[email protected]>> wrote:
>
>
> So, v1 LGTM. Only thing is that I think we can also make
> “mismatching” to “mismatched” in the errmsg.
>
> I agree that "mismatched property names" reads better, so I have updated
> that in v2.
I think the existing wording is better. In any case, you only changed a
few places and not others.
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
@ 2026-05-05 07:43 ` Peter Eisentraut <[email protected]>
2 siblings, 0 replies; 9+ messages in thread
From: Peter Eisentraut @ 2026-05-05 07:43 UTC (permalink / raw)
To: Ayush Tiwari <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>
On 04.05.26 21:57, Ayush Tiwari wrote:
> [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?]
I have fixed that, thanks for pointing it out. We should stick to the
preferred terms.
(I'll look at the rest of your patch in a bit.)
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
@ 2026-05-07 08:45 ` Peter Eisentraut <[email protected]>
2026-05-07 09:04 ` Re: [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-11 06:39 ` Re: [PATCH] Clean up property graph error messages Ashutosh Bapat <[email protected]>
2 siblings, 2 replies; 9+ messages in thread
From: Peter Eisentraut @ 2026-05-07 08:45 UTC (permalink / raw)
To: Ayush Tiwari <[email protected]>; pgsql-hackers; Ashutosh Bapat <[email protected]>
On 04.05.26 21:57, Ayush Tiwari wrote:
> 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 have fixed that.
> 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.
I think that's fine. I don't think the change makes this better.
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-07 08:45 ` Re: [PATCH] Clean up property graph error messages Peter Eisentraut <[email protected]>
@ 2026-05-07 09:04 ` Ayush Tiwari <[email protected]>
1 sibling, 0 replies; 9+ messages in thread
From: Ayush Tiwari @ 2026-05-07 09:04 UTC (permalink / raw)
To: Peter Eisentraut <[email protected]>; +Cc: pgsql-hackers; Ashutosh Bapat <[email protected]>
Hi,
On Thu, 7 May 2026 at 14:15, Peter Eisentraut <[email protected]> wrote:
>
> > 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.
>
> I think that's fine. I don't think the change makes this better.
>
IIUC that is dead code right now, it never reaches that point to release?
Regards,
Ayush
^ permalink raw reply [nested|flat] 9+ messages in thread
* Re: [PATCH] Clean up property graph error messages
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-07 08:45 ` Re: [PATCH] Clean up property graph error messages Peter Eisentraut <[email protected]>
@ 2026-05-11 06:39 ` Ashutosh Bapat <[email protected]>
1 sibling, 0 replies; 9+ messages in thread
From: Ashutosh Bapat @ 2026-05-11 06:39 UTC (permalink / raw)
To: Peter Eisentraut <[email protected]>; +Cc: Ayush Tiwari <[email protected]>; pgsql-hackers
On Thu, May 7, 2026 at 2:15 PM Peter Eisentraut <[email protected]> wrote:
>
> On 04.05.26 21:57, Ayush Tiwari wrote:
> > 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 have fixed that.
>
> > 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.
>
> I think that's fine. I don't think the change makes this better.
>
Yeah.
If we call ReleaseSysCache before ereport(), we need to add local
variables as you have done, which increases the lines of code. Since
ereport will never return, ReleaseSysCache() is not needed at all. But
leaving it there helps justifying fetching the attributes in the
ereport call. FWIW, it makes the code future proof, in a very rare
case if someone makes ereport conditional.
--
Best Wishes,
Ashutosh Bapat
^ permalink raw reply [nested|flat] 9+ messages in thread
end of thread, other threads:[~2026-05-11 06:39 UTC | newest]
Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-04 19:57 [PATCH] Clean up property graph error messages Ayush Tiwari <[email protected]>
2026-05-05 02:50 ` Chao Li <[email protected]>
2026-05-06 06:23 ` Ayush Tiwari <[email protected]>
2026-05-06 06:45 ` Chao Li <[email protected]>
2026-05-07 08:46 ` Peter Eisentraut <[email protected]>
2026-05-05 07:43 ` Peter Eisentraut <[email protected]>
2026-05-07 08:45 ` Peter Eisentraut <[email protected]>
2026-05-07 09:04 ` Ayush Tiwari <[email protected]>
2026-05-11 06:39 ` Ashutosh Bapat <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox