Re: problem with large maintenance_work_mem settings and
| От | Simon Riggs |
|---|---|
| Тема | Re: problem with large maintenance_work_mem settings and |
| Дата | |
| Msg-id | 1141836094.27729.753.camel@localhost.localdomain обсуждение исходный текст |
| Ответ на | Re: problem with large maintenance_work_mem settings and (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: problem with large maintenance_work_mem settings and
|
| Список | pgsql-hackers |
On Wed, 2006-03-08 at 10:45 -0500, Tom Lane wrote: > Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes: > > CREATE INDEX on a 1,8B row table (5 int columns - index created on the > > first row about 300M distinct values): > > > before: 11h 51min > > after: 3h 11min(!) > > Cool. Does it seem to be I/O bound now? Would you be willing to do it > over with oprofile turned on? Very. Any chance of trying it with different maintenance_work_mem settings? Did you try this with trace_sort=on? If so could we get the logs for that? [Results welcome from other hackers...particularly with regard to queries with sort steps in rather than CREATE INDEX.] Best Regards, Simon Riggs
В списке pgsql-hackers по дате отправления: