Re: Memory exhausted (leak?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: apb18(at)cornell(dot)edu, pgsql-general(at)postgresql(dot)org
Subject: Re: Memory exhausted (leak?)
Date: 2004-09-09 21:59:58
Message-ID: 10972.1094767198@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> 1. Are the row estimates accurate? If not increase your statistics.

Presumably not, since he'd surely never overflow memory with hashes of
only a few hundred rows.

The hash join code is capable of splitting the table into multiple
segments, but it won't do so unless the planner's estimate of the
table size is larger than sort_mem. So the real problem IMHO is
the bad rowcount estimate.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-09-09 22:01:30 Re: Where does postgres store records of DROP-ed columns?
Previous Message Aaron Birkland 2004-09-09 21:42:20 Re: Memory exhausted (leak?)