From: Justin Pryzby <pryzby@telsasoft.com>
To: Jürgen Purtz <juergen@purtz.de>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Corey Huinker <corey.huinker@gmail.com>
Cc: Roger Harkavy <rogerharkavy@gmail.com>
Cc: pgsql-hackers@postgresql.org, Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: Add A Glossary
Date: Fri, 20 Mar 2020 18:03:18 -0500
Message-ID: <20200320230318.GB13662@telsasoft.com> (raw)
In-Reply-To: <64b49f34-eaf6-6de2-e951-0eb8d4afabc2@purtz.de>
References: <CADkLM=fwtE-TCU7sRnvaE74z12kOp_A+CdUwMr7aZt39pXbh6A@mail.gmail.com>
<20200320001122.GA19602@alvherre.pgsql>
<20200320195841.GA13662@telsasoft.com>
<64b49f34-eaf6-6de2-e951-0eb8d4afabc2@purtz.de>
On Fri, Mar 20, 2020 at 11:32:25PM +0100, Jürgen Purtz wrote:
> > > + <glossentry id="glossary-file-segment">
> > > + <glossterm>File Segment</glossterm>
> > > + <glossdef>
> > > + <para>
> > > + If a heap or index file grows in size over 1 GB, it will be split
> > 1GB is the default "segment size", which you should define.
>
> ???
"A <<Table>> or other >>Relation<<" is larger than a >Cluster's< segment size
is stored in multiple physical files. This avoids file size limitations which
vary across operating systems."
https://www.postgresql.org/docs/devel/runtime-config-preset.html
ts=# SELECT name, setting, unit, category, short_desc FROM pg_settings WHERE name~'block_size|segment_size';
name | setting | unit | category | short_desc
------------------+----------+------+----------------+----------------------------------------------
block_size | 8192 | | Preset Options | Shows the size of a disk block.
segment_size | 131072 | 8kB | Preset Options | Shows the number of pages per disk file.
wal_block_size | 8192 | | Preset Options | Shows the block size in the write ahead log.
wal_segment_size | 16777216 | B | Preset Options | Shows the size of write ahead log segments.
> > > + <glossentry id="glossary-heap">
> > > + <glossterm>Heap</glossterm>
> > > + <glossdef>
> > > + <para>
> > > + Contains the original values of <glossterm>Row</glossterm> attributes
> > I'm not sure what "original" means here ?
>
> Yes, this may be misleading. I want to express, that values are stored in
> the heap (the 'original') and possibly repeated as a key in an index.
Maybe "this is the content of rows/attributes in >>Tables<< or other >>Relations<<".
or "this is the data store for ..."
> > > + <glossentry id="glossary-host">
> > > + <glossterm>Host</glossterm>
> > > + <glossdef>
> > > + <para>
> > > + See <glossterm>Server</glossterm>.
> > Or client. Or proxy at some layer or other intermediate thing. Maybe just
> > remove this.
>
> Sometimes the term "host" is used in a different meaning. Therefor we shall
> have this glossary entry for clarification that it shall be used only in the
> sense of a "server".
I think that suggests just removing "host" and consistently saying "server".
--
Justin
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: pgsql-hackers@postgresql.org
Cc: pryzby@telsasoft.com, juergen@purtz.de, alvherre@2ndquadrant.com, corey.huinker@gmail.com, rogerharkavy@gmail.com, coelho@cri.ensmp.fr, michael@paquier.xyz
Subject: Re: Add A Glossary
In-Reply-To: <20200320230318.GB13662@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox