Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure
Date
Msg-id 3762a2e0-d3be-40e7-83d2-52dc3e1a21b2@eisentraut.org
Whole thread
In response to Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
List pgsql-hackers
On 28.04.26 17:02, Ashutosh Bapat wrote:
> We are looking up element label catalogs twice in this patch - first
> to find the label to be dropped and then to find the number of labels
> associated with the given element. I combined these two into a single
> while loop.

That looks okay, but I think the names of the local variables are now a 
bit off.  I would expect elrel and elscan to refer to 
pg_propgraph_element, not pg_propgraph_element_label.  Maybe use 
ellabelrel etc.

Also, I think this code needs to think a bit about locking to handle the 
situation where more than one DROP LABEL operation happens concurrently.




pgsql-hackers by date:

Previous
From: Ayush Tiwari
Date:
Subject: Re: [PATCH] Reject ENCODING option for COPY TO FORMAT JSON
Next
From: Peter Eisentraut
Date:
Subject: Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure