read-only GUC variables - supporting doc changes

Started by Joe Conwayover 22 years ago2 messagespatches
Jump to latest
#1Joe Conway
mail@joeconway.com

The attached is the supporting documentation for the read-only GUC
variable changes. Comments?

Thanks,

Joe

Attachments:

guc-read-only-docs.1.patchtext/plain; name=guc-read-only-docs.1.patchDownload+99-0
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Joe Conway (#1)
Re: read-only GUC variables - supporting doc changes

Joe Conway <mail@joeconway.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