| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | AW: [HACKERS] Some notes on optimizer cost estimates |
| Date: | 2000-01-24 17:58:02 |
| Message-ID: | 219F68D65015D011A8E000006F8590C603FDC21C@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Welche | 2000-01-24 17:59:21 | Re: [HACKERS] Re: pg_dump possible fix, need testers. |
| Previous Message | Tom Lane | 2000-01-24 17:53:49 | Re: [HACKERS] Well, then you keep your darn columns |