Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
От | Alexey Ermakov |
---|---|
Тема | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently |
Дата | |
Msg-id | 366f7247-709e-c07c-4875-068be1121c3a@dataegret.com обсуждение исходный текст |
Ответ на | Re: BUG #17268: Possible corruption in toast index after reindex index concurrently (Maxim Boguk <maxim.boguk@gmail.com>) |
Ответы |
Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
|
Список | pgsql-bugs |
Hello, On 2021-11-08 02:29, Maxim Boguk wrote: > On Sun, Nov 7, 2021 at 2:07 AM Andres Freund <andres@anarazel.de> wrote: >> Hi, >> >> On November 4, 2021 1:01:44 PM PDT, Maxim Boguk <maxim.boguk@gmail.com> wrote: >>> UPDATE: the problem base table entry which had erroneous toast data >>> definitely had been created during the REINDEX run of toast idx. >> Do you have any details about the transaction / application that inserted the data? > Well... jdbc with server side prepared statements off (pgbouncer). > I was told that application inserts rows into given table with queries like: INSERT INTO zz (id, body) VALUES (?, ?) ON CONFLICT (id) DO NOTHING inside transaction. It's possible to attempt to insert row with same id several times inside one transaction (in that case usually that id is new one i.e. was not presented in the table before that transaction). Hope it could help in some way. -- Thanks, Alexey Ermakov
В списке pgsql-bugs по дате отправления: