| From: | Chris Withers <chris(at)simplistix(dot)co(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Igor Neyman <ineyman(at)perceptron(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: performance problems with bulk inserts/updates on tsrange with gist-based exclude constrains |
| Date: | 2016-09-19 07:40:00 |
| Message-ID: | 51d6d6ed-2ba6-0add-8ebb-c435c785adbc@simplistix.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16/09/2016 15:29, Tom Lane wrote:
> Chris Withers <chris(at)simplistix(dot)co(dot)uk> writes:
>> On 16/09/2016 14:54, Igor Neyman wrote:
>>> So, what is the value for "end ts", when the record is inserted (the range just started)?
>
>> It's open ended, so the period is [start_ts, )
>
> I've not looked at the GiST range opclass, but I would not be surprised if
> having lots of those is pretty destructive to the index's ability to be
> selective about && searches.
If that's so, that's a little disappointing...
(I'd have thought the special case end value (open ended) and the ending
type (inclusive/exclusive) would just be sentinel values)
How would I verify your suspicions?
cheers,
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kiran | 2016-09-19 08:46:30 | Results in ERROR: syntax error in tsquery: |
| Previous Message | Patrick B | 2016-09-18 21:28:15 | Re: select distinct postgres 9.2 |