Re: GIN data corruption bug(s) in 9.6devel

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN data corruption bug(s) in 9.6devel
Date: 2016-04-28 13:26:38
Message-ID: 57220F8E.8080700@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The more I think about it, the more I think gin is just an innocent
> bystander, for which I just happen to have a particularly demanding
> test. I think something about snapshots and wrap-around may be
> broken.

After 10 hours of running I've got
1587 XX000 2016-04-28 05:57:09.964 MSK:ERROR: unexpected chunk number 0
(expected 1) for toast value 10192986 in pg_toast_16424
1587 XX000 2016-04-28 05:57:09.964 MSK:CONTEXT: automatic analyze of table
"teodor.public.foo"
1587 00000 2016-04-28 05:57:09.974 MSK:LOG: JJ transaction ID wrap limit is
2147484514, limited by database with OID 16384

I've pushed v5 of gin-alone-cleanup patch, many thanks to all participants.
Will work on backpatch

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2016-04-28 13:40:21 Re: [PATCH] amroutine->amsupport from numeric to defined constants
Previous Message Daniel Gustafsson 2016-04-28 13:06:31 Unused macros in contrib code