Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > The second idea is the idea of having one parameter depend on another. > > Not only could we do that for some of our existing parameters, but we > > could have pseudo-parameters like concurrent_queries, memory_usage, and > > extra_disk_space that could be at the top of postgresql.conf and then > > affect the other settings. > > We have tried to do that in the past, and it didn't work well *at all*.
We have? When? > The idea has a fundamental logical flaw, which is that it's not clear > which parameter wins if the user changes both. Yes, you could get into problems by having variable dependency loops, but I see no way to easily improve configuration without it. My idea was to have: memory_usage = 128MB ## pseudo-parameter shared_buffers = $memory_usage * 0.75 -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers