Philip Warner writes:
Just wondering where I should put my modified tuning notes. I was planning
on making them section 3.7 in the Admin guide. Does that sound reasonable?
The frequency of vacuum and analyze would seem to belong under Routine
Vacuuming in the Maintenance chapter. Setting
At 08:55 PM 13/12/2002 +0100, Peter Eisentraut wrote:
The frequency of vacuum and analyze would seem to belong..
...max_fsm_relations belongs...
...Setting max_fsm_pages also belongs in that list...
...parts that refer to the VACUUM output should be put... near the Routine
Vacuuming
Not sure I
Just wondering where I should put my modified tuning notes. I was planning
on making them section 3.7 in the Admin guide. Does that sound reasonable?
The current version can be seen at:
http://www.rhyme.com.au/manuals/pgsql-7.3/postmaster-tuning-software.html
I think it's important we
On Wed, 2002-12-11 at 09:40, Philip Warner wrote:
Just wondering where I should put my modified tuning notes. I was planning
on making them section 3.7 in the Admin guide. Does that sound reasonable?
The current version can be seen at:
At 10:25 AM 11/12/2002 -0500, Robert Treat wrote:
Do you see a 3.8 Tuning the Server
(Hardware) section as well?
Hardware and/or OS. I think Bruce's tuning docs tend to address the
hardware and environmental issues, so I was not planning to write anything
myself.
Philip Warner wrote:
At 10:25 AM 11/12/2002 -0500, Robert Treat wrote:
Do you see a 3.8 Tuning the Server
(Hardware) section as well?
Hardware and/or OS. I think Bruce's tuning docs tend to address the
hardware and environmental issues, so I was not planning to write anything
myself.
I
At 12:10 PM 12/12/2002 +1100, Philip Warner wrote:
good starting point for tuning
I think this probably sums it up.
IMO it is grandiose to call it a tuning document; at best it is a
'Misbehaviour Avoidance' document. We probably need something about the
usual database-side tuning options:
Philip Warner wrote:
At 12:10 PM 12/12/2002 +1100, Philip Warner wrote:
good starting point for tuning
I think this probably sums it up.
IMO it is grandiose to call it a tuning document; at best it is a
'Misbehaviour Avoidance' document. We probably need something about the
usual
At 08:43 PM 11/12/2002 -0500, Bruce Momjian wrote:
Well, it isn't something you would play with regularly, like backups.
How about I call it 'Managing Server Resources' and put it between 'Runtime
Configuration' and 'Managing Kernel Resources'? ie. it becomes 3.5.
At 01:22 AM 12/12/2002 -0500, Tom Lane wrote:
in my mind tuning activities will hold good till your database usage
changes.
What about my later suggestion of 'Managing Server Resources', going before
'Managing Kernel Resources'. Or perhaps, 'Tuning Server Resources'...
The document describes
10 matches
Mail list logo
