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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Alex Guo <guo(dot)alex(dot)hengchen(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fix DROP PROPERTY GRAPH "unsupported object class" error
Date: 2026-06-03 02:21:52
Message-ID: ah-PwIK3wBqh2VpU@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-06-03 02:25:28 Re: pg_createsubscriber: allow duplicate publication names
Previous Message lin teletele 2026-06-03 01:58:40 Re: Use pg_current_xact_id() instead of deprecated txid_current()