Re: read-only GUC variables - supporting doc changes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: read-only GUC variables - supporting doc changes
Date: 2003-12-06 05:22:42
Message-ID: 6823.1070688162@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Joe Conway <mail(at)joeconway(dot)com> writes:
> The attached is the supporting documentation for the read-only GUC
> variable changes. Comments?

Most of this paragraph strikes me as noise:

> + Shows the size of a disk block. It is determined by the value
> + of <literal>BLCKSZ</> when building the server. The default
> + value is 8192 bytes. Each data file (heap or index) is divided
> + into disk blocks which may be thought of as the unit of I/O.
> + A <productname>PostgreSQL</productname> buffer contains exactly
> + one disk block. A <productname>PostgreSQL</productname> disk page
> + is an abstraction layered on top of a disk block. Specifically,
> + while a disk block can be unformatted, a disk page is always a
> + formatted page. The <varname>shared_buffers</varname> setting is
> + influenced by <varname>block_size</varname>. See
> + <xref linkend="runtime-config-resource"> for information.

I think you could drop the middle four sentences ("Each ... formatted page")
without losing much.

Otherwise it looks fine ...

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Joe Conway 2003-12-06 17:38:44 Re: [HACKERS] bytea, index and like operator again and detailed report
Previous Message Joe Conway 2003-12-06 04:56:20 read-only GUC variables - supporting doc changes