Re: GiST support for inet datatypes

From: Emre Hasegeli <emre(at)hasegeli(dot)com>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GiST support for inet datatypes
Date: 2014-02-26 10:49:10
Message-ID: CAE2gYzzP+MGLz2eXbdobzrnfDxMOJ1zVGiXVmXBPc60p7mcoiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2014-02-24 02:44, Andreas Karlsson <andreas(at)proxel(dot)se>:

> Note: The patches do not apply anymore due to changes to
> src/backend/utils/adt/Makefile.

I will fix it on the next version.

> I see, thanks for the explanation. But I am still not very fond of how that
> code is written since I find it hard to verify the correctness of it, but
> have no better suggestions.

We can split the selectivity estimation patch from the GiST support, add
it to the next commit fest for more review. In the mean time, I can
improve it with join selectivity estimation. Testing with different datasets
would help the most to reveal how true the algorithm is.

> Do you think the new index is useful even if you use the basic geo_selfuncs?
> Or should we wait with committing the patches until all selfuncs are
> implemented?

My motivation was to be able to use the cidr datatype with exclusion
constraints. I think the index would also be useful without proper
selectivity estimation functions. Range types also use geo_selfuncs for
join selectivity estimation.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Golub 2014-02-26 11:20:10 Re: 9.5: UPDATE/DELETE .. ORDER BY .. LIMIT ..
Previous Message Christian Kruse 2014-02-26 10:41:28 Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication