Re: posgres 12 bug (partitioned table)

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Biryukov <79166341370(at)yandex(dot)ru>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: posgres 12 bug (partitioned table)
Date: 2020-06-05 00:18:28
Message-ID: CAApHDvqb1ia7Bbn-wHmXxPkgDWRaCZ9uBHN1ak3ajbD0AW3RTg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, 5 Jun 2020 at 04:57, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Reproduced here. The example works in v11, and in v10 if you remove
> the unnecessary-to-the-example primary key, so it seems like a clear
> regression. I didn't dig for the cause but I suppose it's related
> to Andres' slot-related changes.

Looks like c2fe139c20 is the breaking commit.

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2020-06-05 00:20:22 Re: Potential G2-item cycles under serializable isolation
Previous Message Peter Geoghegan 2020-06-04 23:14:20 Re: Potential G2-item cycles under serializable isolation

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-06-05 00:26:15 Re: [PATCH] Keeps tracking the uniqueness with UniqueKey
Previous Message Alvaro Herrera 2020-06-04 23:46:00 Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762