| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Joe Maldonado <jmaldonado(at)mail(dot)webehosting(dot)biz> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postmaster out of memory.... |
| Date: | 2004-02-28 22:24:48 |
| Message-ID: | 20040228222448.GD12519@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 27, 2004 at 01:45:07PM -0500, Joe Maldonado wrote:
> Hello all!
>
> when asking postgres to aggregate totals accross 4.5 or so Million
> records. The visible effect is that the postmaster will grow to the
> 3GB process limit and die without a core :(.
> I have seen this same behaviour discussed back in 6.5 archives in the
> thread with subject "[SQL] How to avoid "Out of memory" using aggregate
> functions? ". Is this fixed? Why is the postmaster exceeding it's 102MB
> sort mem size when doing these queries and not paging out the data?
What version? We aggregate million of value vairly often. What
aggregate?
Have you run ANALYZE recently?
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> If the Catholic church can survive the printing press, science fiction
> will certainly weather the advent of bookwarez.
> http://craphound.com/ebooksneitherenorbooks.txt - Cory Doctorow
| From | Date | Subject | |
|---|---|---|---|
| Next Message | culley harrelson | 2004-02-28 23:46:20 | Korean characters in a SQL_ASCII database?!? |
| Previous Message | Martijn van Oosterhout | 2004-02-28 22:23:02 | Re: Memory usage |