| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How to improve insert speed with index on text column |
| Date: | 2012-02-03 20:54:36 |
| Message-ID: | CAOR=d=2u2ytFJumtdHB+QirgKtRcPChqY8sjqtD-gMzWj8H=kA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jan 31, 2012 at 1:20 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> yeah -- postgresql.conf settings are not going to play a big role here unless:
> *) you defer index build to the end of the load, and do CREATE INDEX
> and crank maintenance_work_mem
> *) you are doing lots of transactions and relax your sync policy via
> synchronous_commit
checkpoint segments sometimes helps for loading large amounts of data.
> what's almost certainly happening here is that the text index is
> writing out a lot more data. what's the average length of your key?
Yeah, the OP really needs to switch to hashes for the indexes. And
like another poster mentioned, it's often faster to use a btree of
hashes than to use the built in hash index type.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-02-03 21:56:15 | Re: How to remove a table statistics ? |
| Previous Message | Kevin Grittner | 2012-02-03 19:03:18 | Re: How to improve insert speed with index on text column |