Re: Extremely slow intarray index creation and inserts.

From: Oleg Bartunov
Subject: Re: Extremely slow intarray index creation and inserts.
Date: ,
Msg-id: Pine.LNX.4.64.0903191531040.31919@sn.sai.msu.ru
(view: Whole thread, Raw)
In response to: Re: Extremely slow intarray index creation and inserts.  (Tom Lane)
Responses: Re: Extremely slow intarray index creation and inserts.  (Oleg Bartunov)
List: pgsql-performance


On Thu, 19 Mar 2009, Tom Lane wrote:

> Oleg Bartunov <> writes:
>> We usually say about 200 unique values as a limit for
>> gist_int_ops.
>
> That seems awfully small ... should we make gist_intbig_ops the default,
> or more likely, raise the signature size of both opclasses?  Even at a
> crossover point of 10000 I'm not sure that many real-world apps would
> bother considering gist_int_ops.

gist__int_ops doesn't uses signatures, it uses range compression, which
is not lossy, but not capacious. Perhaps, that's why we decided to use it
as default opclass.


     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: , http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83


pgsql-performance by date:

From: Bruce Momjian
Date:
Subject: Re: Proposal of tunable fix for scalability of 8.4
From: Anne Rosset
Date:
Subject: Need help with one query