public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jürgen Purtz <[email protected]>
To: Peter Eisentraut <[email protected]>
To: [email protected]
Subject: Re: Additional Chapter for Tutorial
Date: Fri, 11 Sep 2020 09:49:23 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 10.09.20 18:26, Peter Eisentraut wrote:
> On 2020-09-02 09:04, Jürgen Purtz wrote:
>> On 01.09.20 23:30, Peter Eisentraut wrote:
>>> It is mostly advanced low-level information that is irrelevant for
>>> someone starting up,
>> That applies only to the VACUUM chapter. VACUUM and AUTOVACUUM are
>> controlled by a lot of parameters. Therefor the current documentation
>> concerning the two mechanism spreads the description across different
>> pages (20.4, 25.1, VACUUM command). Because of the structure of our
>> documentation that's ok. But we should have a summary page somewhere -
>> not necessarily in the tutorial.
>
> There is probably room for improvement, but the section numbers you 
> mention are not about VACUUM, AFAICT, so I can't really comment on 
> what you have in mind.
>
Because of the additional chapter for the 'tutorial' on my local 
computer, the numbers increased for me. The regular chapter numbers are 
19.4 and 24.1. Sorry for the confusion. In detail:

19.4: parameters to configure the server, especially five parameters 
'vacuum_cost_xxx'.

19.10: parameters to configure autovacuum.

19.11: parameters to configure client connections, especially five 
parameters 'vacuum_xxx' concerning their freeze-behavior.

24.1: explains the general necessity of (auto)vacuum and their strategies.

The page about the SQL command VACUUM explains the different options 
(FULL, FREEZE, ..) and their meaning.

--

Jürgen Purtz

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Additional Chapter for Tutorial
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox