| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Eduardo Almeida <edalmeida(at)yahoo(dot)com> |
| Cc: | Jan Wieck <JanWieck(at)yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] MySQL vs PG TPC-H benchmarks |
| Date: | 2004-04-22 15:54:48 |
| Message-ID: | 7444.1082649288@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-performance |
Eduardo Almeida <edalmeida(at)yahoo(dot)com> writes:
> About 7hs:30min to load the data and 16:09:25 to
> create the indexes
You could probably improve the index-create time by temporarily
increasing sort_mem. It wouldn't be unreasonable to give CREATE INDEX
several hundred meg to work in. (You don't want sort_mem that big
normally, because there may be many sorts happening in parallel,
but in a data-loading context there'll just be one active sort.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-04-22 16:19:47 | Re: [PERFORM] MySQL vs PG TPC-H benchmarks |
| Previous Message | Eduardo Almeida | 2004-04-22 13:59:10 | Re: [PERFORM] MySQL vs PG TPC-H benchmarks |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-04-22 16:19:47 | Re: [PERFORM] MySQL vs PG TPC-H benchmarks |
| Previous Message | Rod Taylor | 2004-04-22 14:46:40 | Re: order by index, and inheritance |