pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-hackers@postgresql.org
Subject: Re: GIN improvements part 1: additional information
Date: Sat, 11 Jan 2014 03:15:35 +0100
Message-ID: <52D0A947.6050706@fuzzy.cz> (raw )
In-Reply-To: <CAPpHfduBDxQ7Tw5bZCCgxmJzNHDRG6eELAuseuCEvKt=dw0Yfw@mail.gmail.com >
References: <CAPpHfdutJEC9+6vWX579afZKzdHKCT2wzDkAEom1XmiXEwF3pw@mail.gmail.com >
<20131106153604.GM5809@eldon.alvh.no-ip.org >
<528CEB34.7080702@vmware.com >
<CAPpHfdvG+EvY26-bRAj=FzUUSm+O+9gc0g7PmM1fupxy2Ycv3g@mail.gmail.com >
<52950F46.2080009@vmware.com >
<CAPpHfds7rT_+6oTyPOQ+XH7dfb6ucnBVrfJc-mbAFrctNy847Q@mail.gmail.com >
<5298615C.7060102@vmware.com >
<5298E834.4090408@vmware.com >
<CAPpHfdvP3G2k04tpCyEA0mAd2e8xOQyuj=2wwAj0UVhB1_oe+g@mail.gmail.com >
<52A58AD5.6030808@vmware.com >
<CAPpHfdvKC9HE_D+BYBUpxqyWSE4UD_=ykZgfSxkAv4P3LBFQjg@mail.gmail.com >
<52A62771.3070800@vmware.com >
<CAPpHfdu2nXxxNCmtMBBiS+3CRdgF8AHCLt2w9Z4s2kKisJSPuA@mail.gmail.com >
<52AEE445.1060206@vmware.com >
<CAPpHfdvK3eZr8iQJtp9ax9k80MKRKkPKgqcc0SB1bn+_KVq-Xg@mail.gmail.com >
<52AF837C.3040201@vmware.com >
<52B2F5B0.1030809@vmware.com >
<52B49C34.8060300@vmware.com >
<CA+HiwqGO91OEE0ZBa0q2RqFEKm5dy5VzXrf7uoYObw9BCKSEVA@mail.gmail.com >
<CAPpHfduBDxQ7Tw5bZCCgxmJzNHDRG6eELAuseuCEvKt=dw0Yfw@mail.gmail.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 8.1.2014 22:58, Alexander Korotkov wrote:
> Thanks for reporting. Fixed version is attached.
I've tried to rerun the 'archie' benchmark with the current patch, and
once again I got
PANIC: could not split GIN page, didn't fit
I reran it with '--enable-cassert' and with that I got
TRAP: FailedAssertion("!(ginCompareItemPointers(&items[i - 1],
&items[i]) < 0)", File: "gindatapage.c", Line: 149)
LOG: server process (PID 5364) was terminated by signal 6: Aborted
DETAIL: Failed process was running: INSERT INTO messages ...
so the assert in GinDataLeafPageGetUncompressed fails for some reason.
I can easily reproduce it, but my knowledge in this area is rather
limited so I'm not entirely sure what to look for.
regards
Tomas
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (119+ messages) latest in thread
Message-ID: <52D0A947.6050706@fuzzy.cz>
Permalink: ../52D0A947.6050706@fuzzy.cz/
Also on: postgresql.org/message-id/52D0A947.6050706@fuzzy.cz
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tv@fuzzy.cz
Subject: Re: GIN improvements part 1: additional information
In-Reply-To: <52D0A947.6050706@fuzzy.cz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox