On Tue, 4 Mar 2003, Greg Stark wrote:
> Oleg Bartunov <oleg@sai.msu.su> writes:
>
> > > db=# CREATE INDEX cache_gist_idx on cache using gist ( foo_id , attribute_set gist__int_ops);
>
> > what's the time to create gist indices separately ? I suppose 15m is the time
> > to create btree index on *single* column ?
>
> Unfortunately I can't run timing tests on it without invalidating whatever
> timing results I get for the current index build which is still running.
>
> postgres 30176 93.7 21.7 68964 56096 ? R 11:08 133:39 postgres: postgres slo [local] CREATE INDEX
>
> 15m was what i remember as the time to build a unique (non-gist) btree index
> on (foo_id,bar_id) where foo_id is the same integer column as the leading
> column in the gist index, and bar_id is another integer column.
>
> There are 1,161,435 records, with 384 distinct values of foo_id. The number of
> records per value of foo_id ranges from 1 to 11,474.
hmm, not so much. We might be interested to play with the data.
How big would be compressed archive of your data, so we could download
it and use as test data.
>
> The annoying thing here is that 99% of the attribute_set columns will have
> exactly one value in them. All this work is for the 1% that can have multiple
> values.
>
> --
> greg
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
Regards, Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83