Baoding-FenShuaJiang
/
Green_GoodERP18_FSJ_Standard
關註 1
收藏 0
Wiki 捐赠
gooderp18绿色标准版
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
目錄樹: 0f75e31513
分支列表 標籤列表
${ item.name }
Create branch ${ searchTerm }
from '0f75e31513'
${ noResults }
Green_GoodERP18_FSJ_Standard/PostgreSQL/doc/postgresql/html/server-shutdown.html

62 line
6.5KB
原始文件 Blame 文件歷史 

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.5. Shutting Down the Server</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="kernel-resources.html" title="18.4. Managing Kernel Resources" /><link rel="next" href="upgrading.html" title="18.6. Upgrading a PostgreSQL Cluster" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">18.5. Shutting Down the Server</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="kernel-resources.html" title="18.4. Managing Kernel Resources">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="runtime.html" title="Chapter 18. Server Setup and Operation">Up</a></td><th width="60%" align="center">Chapter 18. Server Setup and Operation</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="upgrading.html" title="18.6. Upgrading a PostgreSQL Cluster">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="SERVER-SHUTDOWN"><div class="titlepage"><div><div><h2 class="title" style="clear: both">18.5. Shutting Down the Server</h2></div></div></div><a id="id-1.6.5.7.2" class="indexterm"></a><p>

  3.    There are several ways to shut down the database server. You control

  4.    the type of shutdown by sending different signals to the master

  5.    <code class="command">postgres</code> process.

  6. 

  7.    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="systemitem">SIGTERM</span><a id="id-1.6.5.7.3.2.1.1.2" class="indexterm"></a></span></dt><dd><p>

  8.        This is the <em class="firstterm">Smart Shutdown</em> mode.

  9.        After receiving <span class="systemitem">SIGTERM</span>, the server

  10.        disallows new connections, but lets existing sessions end their

  11.        work normally. It shuts down only after all of the sessions terminate.

  12.        If the server is in online backup mode, it additionally waits

  13.        until online backup mode is no longer active.  While backup mode is

  14.        active, new connections will still be allowed, but only to superusers

  15.        (this exception allows a superuser to connect to terminate

  16.        online backup mode).  If the server is in recovery when a smart

  17.        shutdown is requested, recovery and streaming replication will be

  18.        stopped only after all regular sessions have terminated.

  19.       </p></dd><dt><span class="term"><span class="systemitem">SIGINT</span><a id="id-1.6.5.7.3.2.2.1.2" class="indexterm"></a></span></dt><dd><p>

  20.        This is the <em class="firstterm">Fast Shutdown</em> mode.

  21.        The server disallows new connections and sends all existing

  22.        server processes <span class="systemitem">SIGTERM</span>, which will cause them

  23.        to abort their current transactions and exit promptly. It then

  24.        waits for all server processes to exit and finally shuts down.

  25.        If the server is in online backup mode, backup mode will be

  26.        terminated, rendering the backup useless.

  27.       </p></dd><dt><span class="term"><span class="systemitem">SIGQUIT</span><a id="id-1.6.5.7.3.2.3.1.2" class="indexterm"></a></span></dt><dd><p>

  28.       This is the <em class="firstterm">Immediate Shutdown</em> mode.

  29.       The server will send <span class="systemitem">SIGQUIT</span> to all child

  30.       processes and wait for them to terminate.  If any do not terminate

  31.       within 5 seconds, they will be sent <span class="systemitem">SIGKILL</span>.

  32.       The master server process exits as soon as all child processes have

  33.       exited, without doing normal database shutdown processing.

  34.       This will lead to recovery (by

  35.       replaying the WAL log) upon next start-up. This is recommended

  36.       only in emergencies.

  37.       </p></dd></dl></div><p>

  38.   </p><p>

  39.    The <a class="xref" href="app-pg-ctl.html" title="pg_ctl"><span class="refentrytitle"><span class="application">pg_ctl</span></span></a> program provides a convenient

  40.    interface for sending these signals to shut down the server.

  41.    Alternatively, you can send the signal directly using <code class="command">kill</code>

  42.    on non-Windows systems.

  43.    The <acronym class="acronym">PID</acronym> of the <code class="command">postgres</code> process can be

  44.    found using the <code class="command">ps</code> program, or from the file

  45.    <code class="filename">postmaster.pid</code> in the data directory. For

  46.    example, to do a fast shutdown:

  47. </p><pre class="screen">

  48. $ <strong class="userinput"><code>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</code></strong>

  49. </pre><p>

  50.   </p><div class="important"><h3 class="title">Important</h3><p>

  51.     It is best not to use <span class="systemitem">SIGKILL</span> to shut down the

  52.     server.  Doing so will prevent the server from releasing shared memory and

  53.     semaphores.  Furthermore, <span class="systemitem">SIGKILL</span> kills

  54.     the <code class="command">postgres</code> process without letting it relay the

  55.     signal to its subprocesses, so it might be necessary to kill the

  56.     individual subprocesses by hand as well.

  57.    </p></div><p>

  58.    To terminate an individual session while allowing other sessions to

  59.    continue, use <code class="function">pg_terminate_backend()</code> (see <a class="xref" href="functions-admin.html#FUNCTIONS-ADMIN-SIGNAL-TABLE" title="Table 9.83. Server Signaling Functions">Table 9.83</a>) or send a

  60.    <span class="systemitem">SIGTERM</span> signal to the child process associated with

  61.    the session.

  62.   </p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="kernel-resources.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="runtime.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrading.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">18.4. Managing Kernel Resources </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 18.6. Upgrading a <span class="productname">PostgreSQL</span> Cluster</td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1