41.2. how connections are established

postgresql is implemented using a simple "process per user" client/server model. in this model there is one client process connected to exactly one server process. as we do not know ahead of time how many connections will be made, we have to use a master process that spawns a new server process every time a connection is requested. this master process is called postmaster and listens at a specified tcp/ip port for incoming connections. whenever a request for a connection is detected the postmaster process spawns a new server process called postgres. the server tasks (postgres processes) communicate with each other using semaphores and shared memory to ensure data integrity throughout concurrent data access.

the client process can be any program that understands the postgresql protocol described in chapter 43. many clients are based on the c-language library libpq, but several independent implementations of the protocol exist, such as the java jdbc driver.

once a connection is established the client process can send a query to the backend (server). the query is transmitted using plain text, i.e. there is no parsing done in the frontend (client). the server parses the query, creates an execution plan, executes the plan and returns the retrieved rows to the client by transmitting them over the established connection.