X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id EE4C2D1B515
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Tue, 14 Oct 2003 20:32:38 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 85140-05
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Tue, 14 Oct 2003 17:32:09 -0300 (ADT)
Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251])
	by svr1.postgresql.org (Postfix) with ESMTP id C707ED1B516
	for <pgsql-docs@postgresql.org>; Tue, 14 Oct 2003 17:32:05 -0300 (ADT)
Received: (from pgman@localhost)
	by candle.pha.pa.us (8.11.6/8.11.6) id h9EKVup28647;
	Tue, 14 Oct 2003 16:31:56 -0400 (EDT)
From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200310142031.h9EKVup28647@candle.pha.pa.us>
Subject: Re: Need help with SGML again
In-Reply-To: <200310141326.08620.josh@agliodbs.com>
To: josh@agliodbs.com
Date: Tue, 14 Oct 2003 16:31:56 -0400 (EDT)
Cc: pgsql-docs@postgresql.org
X-Mailer: ELM [version 2.4ME+ PL106 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200310/11
X-Sequence-Number: 2031


I see vacuum_mem in "runtime-config-resource-memory".  I assume you just
have to point to that section heading.

---------------------------------------------------------------------------

Josh Berkus wrote:
> Bruce,
> 
> > I have Peter on IM.  Here is his reply:
> 
> If he can come over to IRC, we can have a 3-way.
> 
> > Peter Eisentraut: linking is bad anyway.  tell him not to do it.  if the 
> material cannot be presented sequentially, it's too complicated. 
> > 151255111: ok
> 
> ??? Do we want linking or do we want lots of duplicate text?    
> 
> What I have currently is:
> 
>    <sect2 id="runtime-config-basics">
>     <title>Basic Runtime Setup</title>
> 
>     <para>
>     PostgreSQL's default runtime setup is very conservative, and more 
> appropriate to an
>     old workstation than a modern server machine.  As such, you will certainly 
> want to
>     change some of the runtime settings before running PostgreSQL for the 
> first time.
>     After INITDB, database administrators should change most or all of the 
> following settings,
>     listed in order of how frequently they need adjustment.
>     </para>
>     <itemizedlist>
>     <listitem>tcpip_socket</listitem>
>     <listitem>max_connections</listitem>
>     <listitem>shared_buffers</listitem>
>     <listitem>sort_mem</listitem>
>     <listitem>effective_cache_size</listitem>
>     <listitem>random_tuple_cost</listitem>
>     <listitem>vacuum_mem</listitem>
>     <listitem>max_fsm_pages</listitem>
>     <listitem>checkpoint_segments</listitem>
>     </itemizedlist>
> 
> etc.
> 
> It's obvious to me that for this each of the setting names should be linked to 
> the listitem below for the individual setting.  My only other choice would be 
> to *repeat* the configuration text in the "Basic Setup" section, identical 
> with the text below where the settings are defined.  This does *not* seem 
> effective to me.
> 
> -- 
> -Josh Berkus
>  Aglio Database Solutions
>  San Francisco
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073