Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction
Date: 2021-07-29 21:41:33
Message-ID: CA+hUKG+uRkCpVCfrUb0rTMyEBLhfpsDuW91d9XNT1d-cxEJenQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 28, 2021 at 5:02 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Wed, Jul 28, 2021 at 9:00 AM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> > (Except for read-only-anomaly-3, that causes another
> > assertion fail but I believe that it's not related to the initial issue
> > and deserves another bug report.)
>
> Huh. I tried and failed to find that one with concurrent runs. I'll
> wait for your next report before I do anything, just in case there's a
> connection.

This is indeed an unrelated issue, and much older. After many
kilowatt hours, I reproduced it here and worked out that it comes from
GetSafeSnapshot() not expecting possibleUnsafeConflicts to be empty
when WritableSxactCount == 0. More soon.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-07-29 22:35:01 BUG #17128: minimum numeric 'integer' is -2147483647 not -2147483648 as documented
Previous Message Alvaro Herrera 2021-07-29 21:19:24 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size