Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xA0G7-00000002Ohf-1Umn for pgsql-docs@arkaria.postgresql.org; Fri, 25 Sep 2026 07:22:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xA0G6-0000000H0EX-2Y34 for pgsql-docs@arkaria.postgresql.org; Fri, 25 Sep 2026 07:22:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x9q27-0000000EceF-1cQx for pgsql-docs@lists.postgresql.org; Thu, 24 Sep 2026 20:27:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x9q24-000000015aq-2Rnh for pgsql-docs@lists.postgresql.org; Thu, 24 Sep 2026 20:27:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=UebkIcn0e+Iw1+3SiMsOtyqsb55UqMz2e1dNrdzHiF4=; b=b3pAnJNj2yV2zBhTP5kKvzyYkj 5FwRjmjwtVoy/8ZbWSljqbqWw4EE5qB4Egeev7ieerllrxdfJrSUZ9y3p06+pjQYC1tuLthwrd0iw jdTPS/HlL0DM1wKbkd9mCV5i8BSkCNL4tfBA3JQvKYIpfaDmtSkkxdkl0l+6GN8pdSFdqfWwIoVJ+ 0JXORjOyrvlAhiN4Erx8RfE8ntKk+b+euLgZ3nUvBhJjkiEYVTQ25N2QDxcKPAFKusuSmnhhS1Nsy l+gbSWwf2R5q5nVV89iYrwSJtOvJwAdaqCxPMpjmOWpUID4B1w9TqLPnrS81GKljnsXh/eBw4sDzx 7qAHO0ng==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x9q24-003DKL-2c for pgsql-docs@lists.postgresql.org; Thu, 24 Sep 2026 20:27:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x9q22-00000009G4l-2Mmp for pgsql-docs@lists.postgresql.org; Thu, 24 Sep 2026 20:27:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: [Minor] Improve reading in "1.2 Architectural Fundamentals " tutorial To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: matematica.a3k@gmail.com Reply-To: matematica.a3k@gmail.com, pgsql-docs@lists.postgresql.org Date: Thu, 24 Sep 2026 20:26:17 +0000 Message-ID: <179028157720.1026196.11734567258850512063@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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!