From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Proposal for Grand Unified Configuration scheme |
Date: | 2000-03-07 08:15:31 |
Message-ID: | 19385.952416931@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> The idea here is to unify all the various configuration settings into one
> coherent scheme.
A good goal. Your sketch seems reasonable, but one comment:
> ... For
> example it would be nice if I could start the postmaster with the -F
> option and it would look that up in the grand unified options table (see
> above) and say "ah, that's a per-backend option" and pass it on to the
> backend.
In fact -F is *not* a per-backend option, and certainly we dare not
change it on-the-fly via SET. The setting is useless and even dangerous
unless all backends are behaving the same way (see pghackers archives if
you've forgotten why). More generally, some options are reasonable to
set at any time and some aren't; your mechanism needs to deal with that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jacopo Silva | 2000-03-07 08:45:44 | pSQL auth |
Previous Message | Tom Lane | 2000-03-07 08:08:35 | Re: [HACKERS] Optimizer badness in 7.0 beta |