Horton
Menu

Re: Fix DROP PROPERTY GRAPH "unsupported object class" error

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Alex Guo <guo.alex.hengchen@gmail.com>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-06-03T02:21:52Z
Lists: pgsql-hackers 
On Tue, Jun 02, 2026 at 12:27:19PM +0530, Ashutosh Bapat wrote:
> The objects in those two catalogs can be manipulated using ALTER
> PROPERTY GRAPH ... ALTER VERTEX/EDGE TABLE ... subcommands. If an
> event trigger is used to keep copies of the same property graph on
> multiple different clusters (logical replicas?) in sync, they will
> need to be handed over these objects.

+1.  Even after re-reading the thread again, deciding to skip these
catalogs for the object descriptions still looks like an inconsistent
move compared to all the other catalogs.
--
Michael

Commits

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

  1. Readable identity strings for property graph objects

  2. Handle element label and label property objects in object address functions

  3. Simplify code in objectaddress.c for some property graph objects