Re: issues with range types, btree_gist and constraints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: issues with range types, btree_gist and constraints
Date: 2013-02-04 22:32:18
Message-ID: 26877.1360017138@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tv(at)fuzzy(dot)cz> writes:
> I've managed to further simplify the test-case, and I've verified that
> it's reproducible on current 9.2 and 9.3 branches.

Yeah, I've been able to reproduce it as well. I found what I thought
might be the bug: gbt_var_bin_union() looks like it does the wrong thing
if both ends of the range need to be extended. However, fixing that
doesn't fix your test case, so there's more to it.

> I've been unable to reproduce the bug with just a single text column.

Hm. I noticed a lot of elog complaints about "picksplit method
... doesn't support secondary split", so maybe the bug is in the code
that's trying to deal with that. I've not had time to look closer.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-02-04 22:50:45 palloc unification
Previous Message Simon Riggs 2013-02-04 22:28:10 Re: pgsql: Stamp 9.1.8.