From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Oleksii Kliukin <alexk@hintbits.com>
Cc: pgsql-bugs@lists.postgresql.org, ildus@adjust.com, Chris Travers <chris.travers@adjust.com>
Cc: Nick Babadzhanian <nickb@adjust.com>
Cc: julian.schauder@gmx.de
Subject: Re: postgres crash on concurrent update of inheritance partitioned table
Date: Tue, 28 Jan 2020 18:07:55 +0100
Message-ID: <20200128170755.bq3f27bfkjpt4d4b@development> (raw)
In-Reply-To: <EEF05F66-2871-4786-992B-5F45C92FEE2E@hintbits.com>
References: <EEF05F66-2871-4786-992B-5F45C92FEE2E@hintbits.com>
On Tue, Jan 28, 2020 at 05:17:14PM +0100, Oleksii Kliukin wrote:
>Hello there,
>
>We have experienced a few crashes a day since upgrading to pg 12.1 last
>week, during the process of updating an inheritance-partitioned table by
>several concurrent sessions.
>
>Here’s the reproducer that consistency crashes pg 12.1 (and master) on my
>machine.
>
>Setup:
>
>create table p(flag boolean);
>create table c1() inherits(p);
>create table c2() inherits(p);
>insert into c1 select false from generate_series(1,10);
>insert into c2 select false from generate_series(1,10);
>
>session 1: session 2:
>begin; begin
>update p set flag = true;
> update p set flag = true;
>commit; server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
>
Yeah, I can reproduce it too. If I had to guess, I'd say it's another
bug due to
commit 3fb307bc4a76815f96fec28a0d1525ab3fbbcfb4
Author: Andres Freund <andres@anarazel.de>
Date: Mon Sep 9 05:21:30 2019 -0700
Reorder EPQ work, to fix rowmark related bugs and improve efficiency.
which introduced relsubs_done et al, and perhaps did not get the life
cycle / resetting right. Not sure.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: tomas.vondra@2ndquadrant.com, alexk@hintbits.com, chris.travers@adjust.com, nickb@adjust.com, julian.schauder@gmx.de
Subject: Re: postgres crash on concurrent update of inheritance partitioned table
In-Reply-To: <20200128170755.bq3f27bfkjpt4d4b@development>
* 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