Re: optimizer cost calculation problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: optimizer cost calculation problem
Date
Msg-id 26707.1049160175@sss.pgh.pa.us
Whole thread Raw
In response to Re: optimizer cost calculation problem  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: optimizer cost calculation problem
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.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



pgsql-hackers by date:

Previous
From: "Ed L."
Date:
Subject: Re: index corruption?
Next
From: Joe Conway
Date:
Subject: Re: GROUP BY + join regression in 7.3