Re: optimizer cost calculation problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: optimizer cost calculation problem
Date: 2003-04-01 01:22:55
Message-ID: 26707.1049160175@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> BTW it does not 2 gig, but 1 gig (remember that we do sortmembytes *
> 2) .

Good point. Probably that particular calculation should be
"sortmembytes * 2.0" to force it to double before it can overflow.
But I still think we'd better limit SortMem so that the basic
SortMem*1024 calculation can't overflow (or even come close to overflow,
likely).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2003-04-01 02:04:23 Re: GROUP BY + join regression in 7.3
Previous Message Ed L. 2003-04-01 01:06:35 Re: index corruption?