[Minor] Improve reading in "1.2 Architectural Fundamentals " tutorial

Started by PG Bug reporting form20 days ago2 messagesdocs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/18/tutorial-arch.html
Description:

Where it says:
"As is typical of client/server applications, the client and the server can
be on different hosts. In that case they communicate over a TCP/IP network
connection. You should keep this in mind, because the files that can be
accessed on a client machine might not be accessible **(or might only be
accessible using a different file name)** on the database server machine."

The distinction "(or might only be accessible using a different file name)"
does not add to the concept and degrades reading. I propose to remove it:
"As is typical of client/server applications, the client and the server can
be on different hosts. In that case they communicate over a TCP/IP network
connection. You should keep this in mind, because the files that can be
accessed on a client machine might not be accessible on the database server
machine."

Thanks!

#2Laurenz Albe
laurenz.albe@cybertec.at
In reply to: PG Bug reporting form (#1)
Re: [Minor] Improve reading in "1.2 Architectural Fundamentals " tutorial

On Thu, 2026-09-24 at 20:26 +0000, PG Doc comments form wrote:

Page: https://www.postgresql.org/docs/18/tutorial-arch.html

Where it says:
"As is typical of client/server applications, the client and the server can
be on different hosts. In that case they communicate over a TCP/IP network
connection. You should keep this in mind, because the files that can be
accessed on a client machine might not be accessible **(or might only be
accessible using a different file name)** on the database server machine."

The distinction "(or might only be accessible using a different file name)"
does not add to the concept and degrades reading. I propose to remove it:
"As is typical of client/server applications, the client and the server can
be on different hosts. In that case they communicate over a TCP/IP network
connection. You should keep this in mind, because the files that can be
accessed on a client machine might not be accessible on the database server
machine."

I agree with that proposal.
Do you want to prepare a patch?

Yours,
Laurenz Albe