| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Mark Dilger <hornschnorter(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: WIP: BRIN multi-range indexes |
| Date: | 2018-03-02 04:08:06 |
| Message-ID: | 18526.1519963686@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-02-25 01:30:47 +0100, Tomas Vondra wrote:
>> Note: Currently, this only works with float8-based data types.
>> Supporting additional data types is not a big issue, but will
>> require extending the opclass with "subtract" operator (used to
>> compute distance between values when merging ranges).
> Based on Tom's past stances I'm a bit doubtful he'd be happy with such a
> restriction. Note that something similar-ish also has come up in
> 0a459cec96.
> I kinda wonder if there's any way to not have two similar but not equal
> types of logic here?
Hm. I wonder what the patch intends to do with subtraction overflow,
or infinities, or NaNs. Just as with the RANGE patch, it does not
seem to me that failure is really an acceptable option. Indexes are
supposed to be able to index whatever the column datatype can store.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-03-02 04:10:01 | Re: [HACKERS] Statement-level rollback |
| Previous Message | Michael Paquier | 2018-03-02 04:07:54 | Re: [HACKERS] Creating backup history files for backups taken from standbys |