On Thu, 13 Feb 2003, Bruce Momjian wrote:
> To auto-tune, you would need to monitor swap usage and other stuff that
> may vary too much based on load from other systems. Only the admin
> knows how to answer some of those questions.
No, to "auto-tune" many parameters that currently require manual
On Fri, 2003-02-14 at 03:00, Daniel Kalchev wrote:
> >>>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
>>>Josh Berkus said:
> How about we take this discussion to the Performance List, where it belongs?
I believe the design and addition of code that collects and outputs the usage patterns
of the database (statistics) belongs here.
If we take the approach to providing information to tune PostgreS
>>>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 no
HEY PEOPLE!
How about we take this discussion to the Performance List, where it belongs?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
2 PM
To: Daniel Kalchev
Cc: PostgresSQL Hackers Mailing List; [EMAIL PROTECTED]
Subject: Re: [pgsql-advocacy] [HACKERS] Changing the default
configuration
I imagined they could run pgtune anytime after install to update those
performance parameters. It gives them a one-stop location to at least
do
an
> Sent: Thursday, February 13, 2003 2:22 PM
> To: Daniel Kalchev
> Cc: PostgresSQL Hackers Mailing List; [EMAIL PROTECTED]
> Subject: Re: [pgsql-advocacy] [HACKERS] Changing the default
> configuration
>
>
>
> I imagined they could run pgtune anytime after install to u
