Thanks for the analysis. May I ask how long will it cost normally for such bug fix being released since I'm new to the community? And will it be back port to PG 12?
Hai Wang
发件人: Tom Lane <tgl@sss.pgh.pa.us> 发送时间: 2024年6月12日 4:54 收件人: michael.wanghai.a@outlook.com <michael.wanghai.a@outlook.com> 抄送: Peter Geoghegan <pg@bowt.ie>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> 主题: Re: BUG #18502: Upsert on view returns 42P10 error when condition is an expression
PG Bug reporting form <noreply@postgresql.org> writes: > I have a table, index and view like following: > ``` > CREATE TABLE my_table > ( > id uuid primary key, > data jsonb not null > ); > CREATE UNIQUE INDEX ON my_table ((data ->> 'key')); > CREATE VIEW my_view AS SELECT * FROM my_table; > ``` > The upsert on view returns 42P10 error when I execute the following SQL > ``` > INSERT INTO my_view (id, data) > VALUES ('990cc75c-2e60-4c0d-8bec-9ac976dc03bc'::uuid, > '{ > "key": "value" > }'::jsonb) > ON CONFLICT ((data ->> 'key')) > DO NOTHING; > ```
For the archives' sake: the error being complained of is
ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification
Thanks for the report. The fault lies with infer_arbiter_indexes(), which assumes that it can match the output of RelationGetIndexExpressions or RelationGetIndexPredicate directly to the query without adjusting varnos. That works most of the time, because the INSERT target typically has varno 1, matching the way these trees are stored in the catalogs. But not so much when we've flattened an updatable view; so the match fails even when it should succeed.
