| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Zhang Mingli <zmlpostgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: pg15b4: FailedAssertion("TransactionIdIsValid(xmax) |
| Date: | 2022-09-12 02:34:48 |
| Message-ID: | CA+hUKGK+L=5JtGvC7TVzuuM29KQ+iZi7AU8FizKOY+BszWzHLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 12, 2022 at 2:27 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Mon, Sep 12, 2022 at 02:25:48PM +1200, Thomas Munro wrote:
> > On Mon, Sep 12, 2022 at 1:42 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > > But yesterday I started from initdb and restored this cluster from backup, and
> > > started up sqlsmith, and sent some kill -9, and now got more corruption.
> > > Looks like it took ~10 induced crashes before this happened.
> >
> > $SUBJECT says 15b4, which doesn't have the fix. Are you still using
> > maintainance_io_concurrent=0?
>
> Yeah ... I just realized that I've already forgotten the relevant
> chronology.
>
> The io_concurrency bugfix wasn't included in 15b4, so (if I understood
> you correctly), that might explain these symptoms - right ?
Yeah.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-09-12 02:53:14 | Re: pg15b4: FailedAssertion("TransactionIdIsValid(xmax) |
| Previous Message | Justin Pryzby | 2022-09-12 02:27:58 | Re: pg15b4: FailedAssertion("TransactionIdIsValid(xmax) |