From: | Razvan Surdulescu <surdules(at)yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: INSERT performance |
Date: | 2003-11-04 22:57:16 |
Message-ID: | 20031104225716.24136.qmail@web13909.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> surdules(at)yahoo(dot)com (Razvan Surdulescu) writes:
> > CREATE INDEX idx_field1 ON data(field1);
> > CREATE INDEX idx_field2 ON data(field2);
> > ...
> > CREATE INDEX idx_field20 ON data(field20);
>
> Uh, do you actually need an index on every column?
Yes -- I need to search on all these columns, the size
of the table is expected to get very large, and each
column contains very heterogenous data (so indexing
makes sense).
> It's obvious that the index insertions are where the
> time is going.
> You're getting close to 900 index insertions per
> second, which is not
> bad at all on consumer-grade ATA disk hardware, if
> you ask me.
That's helpful to know -- thanks.
> It might
> help to raise shared_buffers, if you didn't already
> do that ... but the
> real solution here is to only index the columns that
> you are actually
> intending to search on.
I will look into the shared_buffers setting -- I have
not done anything with it thus far.
Razvan.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2003-11-04 23:25:23 | Re: SELECT question |
Previous Message | Tom Lane | 2003-11-04 21:35:55 | Re: INSERT performance |