pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Alexey Ermakov <alexey.ermakov@dataegret.com>
To: Maxim Boguk <maxim.boguk@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
Date: Mon, 8 Nov 2021 17:04:40 +0600
Message-ID: <366f7247-709e-c07c-4875-068be1121c3a@dataegret.com> (raw)
In-Reply-To: <CAK-MWwQGv-wjcSrYeGE8fCW0=KYGE1tSMoH-fJ8maWV3kfe9iQ@mail.gmail.com>
References: <17268-d2fb426e0895abd4@postgresql.org>
	<CAH2-Wznen2nOrUB32LrsuF4uGfDF1s_VZzDjhOYfLKo5H1g8Yw@mail.gmail.com>
	<CAK-MWwQBMWOwEJx+DCTnXOrqjg00wMbXwc60hkZD=Q9WmUsChg@mail.gmail.com>
	<CAH2-Wz=Sk=5WCt1T+7cReAuDoggJkiNxeCD73ODm6jfrLu4y1w@mail.gmail.com>
	<CAK-MWwTFEPE+9VJVh_T4HQa5ZH28MgOfHiznk05-Zj+ZnZn2RQ@mail.gmail.com>
	<CAK-MWwTEWO2zzV-1ddm2mpurdv_3wAXwB3u_eh5W7xHM+SrsMQ@mail.gmail.com>
	<E6013BD3-5114-4338-AA03-7FBBE23FEC33@anarazel.de>
	<CAK-MWwQGv-wjcSrYeGE8fCW0=KYGE1tSMoH-fJ8maWV3kfe9iQ@mail.gmail.com>

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






view thread (28+ messages)  latest in thread

Message-ID: <366f7247-709e-c07c-4875-068be1121c3a@dataegret.com>
Permalink:  ../366f7247-709e-c07c-4875-068be1121c3a@dataegret.com/
Also on:    postgresql.org/message-id/366f7247-709e-c07c-4875-068be1121c3a@dataegret.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: alexey.ermakov@dataegret.com, maxim.boguk@gmail.com, andres@anarazel.de, pgsql-bugs@lists.postgresql.org, pg@bowt.ie, michael@paquier.xyz
  Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently
  In-Reply-To: <366f7247-709e-c07c-4875-068be1121c3a@dataegret.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox