public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Jürgen Purtz <[email protected]>
To: [email protected]
Subject: Re: Shrinking SVG (Again)
Date: Wed, 15 Jan 2020 23:25:00 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Wed, 2020-01-15 at 14:56 +0100, Jürgen Purtz wrote:
> I plan to deliver 3 more graphics, see attachment. When creating their
> textual description in the SGML files I faced a problems: The patch of
> GSoD
> https://www.postgresql.org/message-id/flat/CAEkD-mBFQb61gHNWR0cN5K4G4q-i1PRwNn_OKVkKSaaJa5_LbA%40mai...
> is not yet committed. But this chapter is a good place for the graphics.
> Will the GSoD patch become part of the documentation?
Both Tom and me showed interest, and the feedback was that some things
could be improved. I have not heard back from the author since;
I hope she didn't get discouraged.
There were definitely some things there that shouldn't go to waste.
> Any comments? Errors in the graphics? Suggestions? What's about the GSoD
> patch?
I particularly like the first image with the memory and process architecture.
Some mistakes:
- wal_buffers is shared memory, but it is not a part of shared_buffers
- The process that performs most of the writes to the data files is
the checkpointer. Sometimes backends also have to write to data
files.
Minor quibbles:
- The "server process" is traditionally called "backend process"
- "Special purpose memory" is strange.
I thing "private memory" would be better.
I don't know how it could be depicted that each of the backends
has his own.
I liked the "cluster / database / schema" image less.
Some problems:
- No user data should be stored in the "postgres" database.
- "template0" has *no* other schemas or tables.
It must be absolutely empty.
- I am missing the global objects like roles and tablespaces
"outside" the databases.
I am fine with the directory layout image, but I wonder what
"fluctuating states" may be.
Yours,
Laurenz Albe
view thread (7+ messages) latest in thread
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: Shrinking SVG (Again)
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