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 Chao Li
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 42586CE9-15C1-42C2-A75D-50FD4B949141@gmail.com
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  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers

> On May 4, 2026, at 22:47, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 29.04.26 14:58, Chao Li wrote:
>> As Alvaro commented at [1], I added 0003 to use OidIsValid macro. 0001 and 0002 are unchanged.
>> [1]https://www.postgresql.org/message-id/02fe13db-4fba-4e9d-9b4c- e6271a133502@app.fastmail.com
>
> I'm personally not on board with that coding style rule.  At least I don't consider this patch necessary right now as
we'reworking toward stabilizing the current code. 
>

In the current code in propgraphcmds.c, the style is already inconsistent. I see three forms:

At line 434:
```
            if (OidIsValid(opc))
```

At line 754:
```
    if (!labeloid)
```

At lne 1302:
```
    if (pgrelid == InvalidOid)
```

Anyway, I don’t have a strong opinion here, so please feel free to discard 0003.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/







pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Chao Li
Date:
Subject: Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE