Re: ANALYZE on parent table results in an error "tuple already updated by self"

From: Andres Freund <andres(at)anarazel(dot)de>
To: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: ANALYZE on parent table results in an error "tuple already updated by self"
Date: 2019-07-24 02:15:55
Message-ID: 20190724021555.vnytr6ihqeuqjm2p@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2019-07-24 03:19:19 +0200, Manuel Rigger wrote:
> Hi everyone,
>
> In the example below, ANALYZE unexpectedly results in an error.
>
> CREATE TABLE t0(c0 boolean , c1 integer);
> CREATE TABLE t1(c0 boolean, c1 integer) INHERITS(t0);
> INSERT INTO t0(c1) VALUES (0);
> CREATE STATISTICS s0 ON c0, c1 FROM t0;
> ANALYZE t0; -- unexpected: ERROR: tuple already updated by self
>
> I found this on the latest trunk version.

Yea, that's the bug I was referencing earlier in your other thread:
https://www.postgresql.org/message-id/20190619000837.awy6j7h45ahd4vop%40alap3.anarazel.de

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-07-24 02:32:16 Re: ANALYZE on parent table results in an error "tuple already updated by self"
Previous Message Manuel Rigger 2019-07-24 01:19:19 ANALYZE on parent table results in an error "tuple already updated by self"