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

Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, 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-18T05:41:31Z
Lists: pgsql-hackers
On Wed, Jun 17, 2026 at 10:44 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Jun 10, 2026 at 04:30:24PM +0530, Ashutosh Bapat wrote:
> > The term "element" comes later "label v1 of element v1".   There's
> > nothing in the standard called "element label". That term is an
> > artifact of our implementation. I think "label v1 of element v1" reads
> > better and follows the standard compared to "element label v1 of
> > element v1".
>
> [ ... checks 9075-16-2023 ... ]
>
> The term is "element table label" when referring to a clause, and most
> of the places refer to only "label", so I guess that I'm fine with
> your wording here.
> --
> Michael

Thanks for the confirmation.

Since the original bug, which led to creating a PG 19 open item, is
fixed I am moving the open item to the resolved section.

IIUC, the follow-on discussion seems to have concluded and Michael is
fine with the last version of patch. It feels like we need to commit
that patch. Michael, are you going to commit it or do you expect
somebody else to do it?

-- 
Best Wishes,
Ashutosh Bapat



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