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

From scott.marlowe
Subject Re: optimizer cost calculation problem
Date
Msg-id Pine.LNX.4.33.0304010910090.13402-100000@css120.ihs.com
Whole thread Raw
In response to Re: optimizer cost calculation problem  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: optimizer cost calculation problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 31 Mar 2003, Tom Lane wrote:

> 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).

This isn't really an issue for 64 bit hardware is it?



pgsql-hackers by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Dangling backends on win32 7.2.1 port (peerdirect).
Next
From: Tom Lane
Date:
Subject: Re: optimizer cost calculation problem