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

From Thomas Lockhart
Subject Re: AW: AW: [HACKERS] Some notes on optimizer cost estimates
Date
Msg-id 3891BD44.3296FAD7@alumni.caltech.edu
Whole thread Raw
In response to Re: AW: AW: [HACKERS] Some notes on optimizer cost estimates  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: AW: AW: [HACKERS] Some notes on optimizer cost estimates
List pgsql-hackers
> > Independent of this, I thought numerous times (when similar "tuning"
> > issues came up) that it's time for a real unified configuration file,
> > which includes pg_options, the geqo what-not, an option for each of these
> > backend tuning options (join methods, fsync), heck maybe even the port
> > number and an alternative location for temp/sort files. Kind of put all
> > the administration in one place. Something to think about maybe.
> Added to TODO:
>         * Unify configuration into one configuration file

... and that is a good example of database design because?? ;)

It may be the right thing to do, but I can see why an RDBMS project
would have trouble with the concept...
                    - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: [HACKERS] postgres under gdb
Next
From: Tom Lane
Date:
Subject: Re: AW: AW: [HACKERS] Some notes on optimizer cost estimates