Re: Extremely slow intarray index creation and inserts.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Extremely slow intarray index creation and inserts.
Date: 2009-03-19 12:25:26
Message-ID: 25559.1237465526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> 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.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Oleg Bartunov 2009-03-19 12:38:38 Re: Extremely slow intarray index creation and inserts.
Previous Message Glyn Astill 2009-03-19 11:37:11 Re: Prepared statement does not exist