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?
-Joe Maldonado
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
