Re: SP-GiST bug and fix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SP-GiST bug and fix
Date: 2013-11-02 20:26:32
Message-ID: 13867.1383423992@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Teodor Sigaev <teodor(at)sigaev(dot)ru> writes:
> SP-GiST has a bug during creation:
> % create table ranges as select int4range( (random()*5)::int,
> (random()*5)::int+5) as range
> from generate_series(1,1000000) x;

> % create index ranges_range_spgist_idx on ranges using spgist(range);
> ERROR: unexpected spgdoinsert() failure

> Bug is discovered by Jonathan S. Katz <jonathan(dot)katz(at)excoventures(dot)com>

> When it was found deadlock possibility it was fixed by using
> ConditionalLockBuffer() instead of LockBuffer(EXCLUSIVE) and retrying insertion
> from the scratch. Build index method doesn't believe in concurrent access and
> throws an error if ConditionalLockBuffer() fails. But I missed that
> checkpointer process could take a share lock on buffer to write it on disk.

> Attached patch just intoduces retrying during index creation.

The comments could use some work (both here and in spgdoinsert), but
I agree this is a real bug and the fix is sane. Will fix the comments
and commit.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-11-02 22:28:13 Re: Creating Empty Index
Previous Message Peter Eisentraut 2013-11-02 19:32:13 pg_ctl status with nonexistent data directory