Re: Is there a point to having both a normal gist indexand an exclude index?
От | Bruno Wolff III |
---|---|
Тема | Re: Is there a point to having both a normal gist indexand an exclude index? |
Дата | |
Msg-id | 20170405180411.GA8320@wolff.to обсуждение исходный текст |
Ответ на | Is there a point to having both a normal gist index and an excludeindex? (Bruno Wolff III <bruno@wolff.to>) |
Ответы |
Re: Is there a point to having both a normal gist index andan exclude index?
Re: Is there a point to having both a normal gist index and an exclude index? |
Список | pgsql-general |
On Wed, Apr 05, 2017 at 00:05:31 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote: >Bruno Wolff III <bruno@wolff.to> writes: >> ... I create both a normal gist index and an exclude index using the >> following: >> CREATE INDEX contains ON iplocation USING gist (network inet_ops); >> ALTER TABLE iplocation >> ADD CONSTRAINT overlap EXCLUDE USING gist (network inet_ops WITH &&); > >> But I am wondering if it is useful to have the normal gist index for >> finding netblocks containing a specific IP address, as it seems like the >> exclude index should be usable for that as well. > >No, that manually-created index is completely redundant with the >constraint index. Thanks. P.S. Using spgist with version 10 for the exclude index is much faster than using gist in 9.6. I have run the index creation for as long as 6 hours and it hasn't completed with 9.6. It took less than 10 minutes to create it in 10. For this project using 10 isn't a problem and I'll be doing that.
В списке pgsql-general по дате отправления: