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: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
