From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/tutorial-arch.html | 49 ++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 doc/src/sgml/html/tutorial-arch.html (limited to 'doc/src/sgml/html/tutorial-arch.html') diff --git a/doc/src/sgml/html/tutorial-arch.html b/doc/src/sgml/html/tutorial-arch.html new file mode 100644 index 0000000..f123008 --- /dev/null +++ b/doc/src/sgml/html/tutorial-arch.html @@ -0,0 +1,49 @@ + +1.2. Architectural Fundamentals
1.2. Architectural Fundamentals
Prev UpChapter 1. Getting StartedHome Next

1.2. Architectural Fundamentals

+ Before we proceed, you should understand the basic + PostgreSQL system architecture. + Understanding how the parts of + PostgreSQL interact will make this + chapter somewhat clearer. +

+ In database jargon, PostgreSQL uses a + client/server model. A PostgreSQL + session consists of the following cooperating processes + (programs): + +

  • + A server process, which manages the database files, accepts + connections to the database from client applications, and + performs database actions on behalf of the clients. The + database server program is called + postgres. + +

  • + The user's client (frontend) application that wants to perform + database operations. Client applications can be very diverse + in nature: a client could be a text-oriented tool, a graphical + application, a web server that accesses the database to + display web pages, or a specialized database maintenance tool. + Some client applications are supplied with the + PostgreSQL distribution; most are + developed by users. +

+

+ 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 PostgreSQL server can handle + multiple concurrent connections from clients. To achieve this it + starts (“forks”) a new process for each connection. + From that point on, the client and the new server process + communicate without intervention by the original + postgres process. Thus, the + supervisor server process is always running, waiting for + client connections, whereas client and associated server processes + come and go. (All of this is of course invisible to the user. We + only mention it here for completeness.) +

Prev Up Next
1.1. Installation Home 1.3. Creating a Database
\ No newline at end of file -- cgit v1.2.3