From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/server-shutdown.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/server-shutdown.html') diff --git a/doc/src/sgml/html/server-shutdown.html b/doc/src/sgml/html/server-shutdown.html index a32398f..82eaf3d 100644 --- a/doc/src/sgml/html/server-shutdown.html +++ b/doc/src/sgml/html/server-shutdown.html @@ -1,5 +1,5 @@ -19.5. Shutting Down the Server
19.5. Shutting Down the Server
Prev UpChapter 19. Server Setup and OperationHome Next

19.5. Shutting Down the Server

+19.5. Shutting Down the Server

19.5. Shutting Down the Server
Prev UpChapter 19. Server Setup and OperationHome Next

19.5. Shutting Down the Server

There are several ways to shut down the database server. Under the hood, they all reduce to sending a signal to the supervisor postgres process. @@ -63,4 +63,4 @@ $ kill -INT `head -1 /usr/local/pgsql/data/postm continue, use pg_terminate_backend() (see Table 9.88) or send a SIGTERM signal to the child process associated with the session. -

Prev Up Next
19.4. Managing Kernel Resources Home 19.6. Upgrading a PostgreSQL Cluster
\ No newline at end of file +

Prev Up Next
19.4. Managing Kernel Resources Home 19.6. Upgrading a PostgreSQL Cluster
\ No newline at end of file -- cgit v1.2.3