Re: [Bug] Add the missing RTE_GRAPH_TABLE case to transformLockingClause() - Mailing list pgsql-hackers

From Zhenwei Shang
Subject Re: [Bug] Add the missing RTE_GRAPH_TABLE case to transformLockingClause()
Date
Msg-id CABv9HUnGQe7dFYPy=R349_-sm9UjB4uCoOviPWUV_yijWpP0BA@mail.gmail.com
Whole thread
In response to [Bug] Add the missing RTE_GRAPH_TABLE case to transformLockingClause()  (SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>)
List pgsql-hackers
在 2026/5/7 15:37, SATYANARAYANA NARLAPURAM 写道:
> Hi Hackers,
>
> Add the missing RTE_GRAPH_TABLE case to transformLockingClause().
> Without this four
> row-locking strengths applied to a GRAPH_TABLE alias triggers not give
> a user friendly
> error message.
>
> Repro:
>
>   CREATE TABLE v(id int PRIMARY KEY, vname text);
>   CREATE PROPERTY GRAPH g VERTEX TABLES (v);
>   SELECT * FROM GRAPH_TABLE(g MATCH (a) COLUMNS (a.vname)) gt
>     FOR UPDATE OF gt;
>   -- ERROR:  unrecognized RTE type: 8
>
> Attached a patch that returns ERRCODE_FEATURE_NOT_SUPPORTED "FOR ...
> cannot be
> applied to a GRAPH_TABLE" with a position pointer, matching the
> convention used by
> the function/tablefunc etc. Patch includes tests for all four locking
> strengths.
> Since the code path looks simple we can just keep one of them as well
> and trim other
> tests. Thoughts?
>
> Thanks,
> Satya

The change is straightforward, clearly an improvement to me. I think you
may keep all 4 cases as they are light.

Regards,
Zhenwei Shang



pgsql-hackers by date:

Previous
From: Nitin Motiani
Date:
Subject: Re: Adding pg_dump flag for parallel export to pipes
Next
From: Jim Jones
Date:
Subject: Re: Fix bug with accessing to temporary tables of other sessions