Re: [HACKERS] Changing the default configuration - Mailing list pgsql-advocacy

From Daniel Kalchev
Subject Re: [HACKERS] Changing the default configuration
Date
Msg-id 200302140800.h1E80SY04664@dcave.digsys.bg
Whole thread Raw
In response to Re: [HACKERS] Changing the default configuration  (Jason Hihn <jhihn@paytimepayroll.com>)
Responses Re: [HACKERS] Changing the default configuration
List pgsql-advocacy
>>>Jason Hihn said:
 > Pardon my ignorance, but there's no way to auto-tune? Ship it with a thread
 > that gathers statistics and periodically re-tunes the database parameters.
 > Of course, be able to turn it off. People that actually take the time to run
 > tune manually will turn it off as to not have the overhead or interruption.
 > Those that don't care about pg_tune shouldn't care about having a thread
 > around retuning. Those that will care will tune manually.

This is related to my proposition, but trouble is, there is not such thing as
'well tuned database' that will suit all queries. You can tune the database to
the hardware for example (still remember that old argument on random access
and fast disks).

It seems the system could 'self-tune' itself on minor choices. I believe it
does this today for a number of things already. More significant changes
require the DBA consent and choice - but they need to be well informed of the
current usage statistics when making the choice.

Daniel


pgsql-advocacy by date:

Previous
From: Daniel Kalchev
Date:
Subject: Re: [HACKERS] Changing the default configuration
Next
From: Daniel Kalchev
Date:
Subject: Re: [HACKERS] Changing the default configuration