From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | exclusion(at)gmail(dot)com |
Subject: | BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already updated by self |
Date: | 2024-01-25 04:00:01 |
Message-ID: | 18310-1eb233c5908189c8@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18310
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)com
PostgreSQL version: 16.1
Operating system: Ubuntu 22.04
Description:
[ this bug reported to fix defects discovered while working on bug #18297
]
The following query:
CREATE ROLE u;
DROP ROLE u, u;
fails with
ERROR: tuple already updated by self
Whilst all the other DROP commands, accepting a list of objects (namely,
AGGREGATE, DOMAIN, EXTENSION, FOREIGN DATA WRAPPER, FOREIGN TABLE,
FUNCTION, INDEX, MATERIALIZED VIEW, OPERATOR, PROCEDURE, ROUTINE,
SEQUENCE, SERVER, STATISTICS, TABLE, TYPE, VIEW), handle such duplicates
with no error.
Also, the following ALTER query:
CREATE TEXT SEARCH CONFIGURATION ispell_tst (COPY=english);
CREATE TEXT SEARCH DICTIONARY ispell (Template=ispell,
DictFile=ispell_sample, AffFile=ispell_sample);
ALTER TEXT SEARCH CONFIGURATION ispell_tst ALTER MAPPING FOR word, word
WITH ispell;
fails with the same
ERROR: tuple already updated by self
Again, I re-checked all the other ALTER commands, that accept a list of
objects, and could not find other ones producing the same error.
From | Date | Subject | |
---|---|---|---|
Next Message | Jason ChenTJ (CN) | 2024-01-25 04:01:03 | 回复: [External]Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment |
Previous Message | Amit Kapila | 2024-01-25 03:58:31 | Re: BUG #18280: logical decoding build wrong snapshot for subtransactions |