Re: Strategy for doing number-crunching
От
Tom Lane
Тема
Re: Strategy for doing number-crunching
Дата
Msg-id
22136.1325711481@sss.pgh.pa.us
Ответ на
Re: Strategy for doing number-crunching (Matthew Foster)
Список
Дерево обсуждения
Strategy for doing number-crunching Matthew Foster <matthew.foster@noaa.gov>
Re: Strategy for doing number-crunching Tom Lane <tgl@sss.pgh.pa.us>
Re: Strategy for doing number-crunching Matthew Foster <matthew.foster@noaa.gov>
Re: Strategy for doing number-crunching Tom Lane <tgl@sss.pgh.pa.us>
Re: Strategy for doing number-crunching Matthew Foster <matthew.foster@noaa.gov>
Re: Strategy for doing number-crunching "Jean-Yves F. Barbier" <12ukwn@gmail.com>
Re: Strategy for doing number-crunching János Löbb <janos.lobb@yale.edu>
Re: Strategy for doing number-crunching Sean Davis <sdavis2@mail.nih.gov>
Re: Strategy for doing number-crunching "ktm@rice.edu" <ktm@rice.edu>
Re: Strategy for doing number-crunching Sean Davis <sdavis2@mail.nih.gov>
Re: Strategy for doing number-crunching Joe Conway <mail@joeconway.com>
Matthew Foster writes: > On Wed, Jan 4, 2012 at 10:48 AM, Tom Lane wrote: >> Matthew Foster writes: >>> We have a database with approximately 130M rows, and we need to produce >>> statistics (e.g. mean, standard deviation, etc.) on the data. Right now, >>> we're generating these stats via a single SELECT, and it is extremely >>> slow...like it can take hours to return results. >> What datatype are the columns being averaged? If "numeric", consider >> casting to float8 before applying the aggregates. You'll lose some >> precision but it'll likely be orders of magnitude faster. > The data are type double. Hmm. In that case I think you have some other problem that's hidden in details you didn't show us. It should not take "hours" to process only 130M rows. This would best be taken up on pgsql-performance; please see http://wiki.postgresql.org/wiki/Slow_Query_Questions regards, tom lane
В списке pgsql-novice по дате отправления