AW: [HACKERS] Some notes on optimizer cost estimates - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: [HACKERS] Some notes on optimizer cost estimates
Date
Msg-id 219F68D65015D011A8E000006F8590C603FDC21C@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: [HACKERS] Some notes on optimizer cost estimates
Re: AW: [HACKERS] Some notes on optimizer cost estimates
List pgsql-hackers
> > Couldn't we test some of these parameters inside configure and set
> > them there?
> 
> If we could figure out a reasonably cheap way of estimating these
> numbers, it'd be worth setting up custom values at installation time.

Imho this whole idea is not so good. (Sorry)

My points are:
1. even if it is good for an optimizer to be smart,it is even more important, that it is predictable
2. I compile on test machine, production is completely different(more processors, faster disks and controllers)

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Well, then you keep your darn columns
Next
From: Patrick Welche
Date:
Subject: Re: [HACKERS] Re: pg_dump possible fix, need testers.