| From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
| Subject: | Fix DROP PROPERTY GRAPH "unsupported object class" error |
| Date: | 2026-04-22 16:19:26 |
| Message-ID: | aej1DkLwhyZWmtxJ@bdtpg |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
While testing the Property Graphs, I observed that DROP PROPERTY GRAPH could
generate the "unsupported object class" error.
Indeed, getObjectTypeDescription() and getObjectIdentityParts() are missing switch
cases for PropgraphElementLabelRelationId and PropgraphLabelPropertyRelationId,
causing DROP PROPERTY GRAPH to hit the default case and error out with
"unsupported object class".
The bug only manifests when an event trigger is active, because that is what
calls these functions.
The attached adds the missing cases so that DROP PROPERTY GRAPH, DROP PROPERTY GRAPH
IF EXISTS, and DROP SCHEMA CASCADE on schemas containing property graphs all work
correctly when event triggers are present.
It also adds test cases that create an event trigger and then exercise DROP PROPERTY
GRAPH and DROP SCHEMA CASCADE with property graphs.
I think that's worth an open item and I'll add one for this issue.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-DROP-PROPERTY-GRAPH-unsupported-object-class-.patch | text/x-diff | 8.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-04-22 17:01:01 | Re: Fix pg_upgrade to detect invalid logical replication slots on PG19 |
| Previous Message | Fujii Masao | 2026-04-22 16:11:53 | Re: pg_test_timing: fix unit typo and widen diff type |