| From: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Eduardo Almeida <edalmeida(at)yahoo(dot)com>, Jan Wieck <JanWieck(at)yahoo(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [pgsql-advocacy] MySQL vs PG TPC-H benchmarks |
| Date: | 2004-04-22 18:20:47 |
| Message-ID: | 1082658047.4524.0.camel@yarrow.bertheau.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-performance |
В Чтв, 22.04.2004, в 17:54, Tom Lane пишет:
> 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.)
Doesn't this provide a reason for CREATE INDEX not to honour sort_mem?
--
Markus Bertheau <twanger(at)bluetwanger(dot)de>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-22 19:22:51 | Re: [pgsql-advocacy] MySQL vs PG TPC-H benchmarks |
| Previous Message | Josh Berkus | 2004-04-22 18:19:55 | Press Release Party |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-04-22 18:31:22 | Re: Wierd context-switching issue on Xeon patch for 7.4.1 |
| Previous Message | Josh Berkus | 2004-04-22 18:11:43 | Re: Wierd context-switching issue on Xeon patch for 7.4.1 |