Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
pg_ctl(1)
Edit
PageHistory
Diff
Info
LikePages
PG_CTL !!!PG_CTL NAME SYNOPSIS DESCRIPTION EXAMPLES BUGS SEE ALSO ---- !!NAME pg_ctl - start, stop, or restart a PostgreSQL server !!SYNOPSIS __pg_ctl start__ [[ __-w__ ] [[ __-s__ ] [[ __-D__ ''datadir'' ] [[ __-l__ ''filename'' ] [[ __-o__ ''options'' ] [[ __-p__ ''path'' ] __pg_ctl stop__ [[ __-W__ ] [[ __-s__ ] [[ __-D__ ''datadir'' ] [[ __-m s[[mart]__ | __f[[ast]__ | __i[[mmediate]__ ] __pg_ctl restart__ [[ __-w__ ] [[ __-s__ ] [[ __-D__ ''datadir'' ] [[ __-m s[[mart]__ | __f[[ast]__ | __i[[mmediate]__ ] [[ __-o__ ''options'' ] __pg_ctl reload__ [[ __-s__ ] [[ __-D__ ''datadir'' ] __pg_ctl status__ [[ __-D__ ''datadir'' ] !!DESCRIPTION __pg_ctl__ is a utility for starting, stopping, or restarting postmaster(1), the PostgreSQL backend server, or displaying the status of a running postmaster. Although the postmaster can be started manually, __pg_ctl__ encapulates tasks such as redirecting log output, properly detaching from the terminal and process group, and it provides convenient options for controlled shutdown. In __start__ mode, a new postmaster is launched. The server is started in the background, the standard input attached to ''/dev/null''. The standard output and standard error are either appended to a log file, if the __-l__ option is used, or are redirected to __pg_ctl__'s standard output (not standard error). If no log file is chosen, the standard output of __pg_ctl__ should be redirected to a file or piped to another process, for example a log rotating program, otherwise the postmaster will write its output the the controlling terminal (from the background) and will not leave the shell's process group. In __stop__ mode, the postmaster that is running in the specified data directory is shut down. Three different shutdown methods can be selected with the __-m__ option: ``Smart'' mode waits for all the clients to disconnect. This is the default. ``Fast'' mode does not wait for clients to disconnect. All active transactions are rolled back and clients are forcibly disconnected, then the database is shut down. ``Immediate'' mode will abort all server processes without clean shutdown. This will lead to a recovery run on restart. __restart__ mode effectively executes a stop followed by a start. This allows the changing of postmaster command line options. __reload__ mode simply sends the postmaster a __SIGHUP__ signal, causing it to reread its configuration files (''postgresql.conf'', ''pg_hba.conf'', etc.). This allows changing of configuration-file options that do not require a complete restart to take effect. __status__ mode checks whether a postmaster is running and if so displays the PID and the command line options that were used to invoke it. __OPTIONS__ __-D__ ''datadir'' Specifies the file system location of the database files. If this is omitted, the environment variable __PGDATA__ is used. __-l__ ''filename'' Append the server log output to ''filename''. If the file does not exist, it is created. The umask is set to 077, so access to the log file from other users is disallowed by default. __-m__ ''mode'' Specifies the shutdown mode. ''mode'' may be smart, fast, or immediate, or the first letter of one of these three. __-o__ ''options'' Specifies options to be passed directly to __postmaster__. The parameters are usually surrounded by single or double quotes to ensure that they are passed through as a group. __-p__ ''path'' Specifies the location of the ''postmaster'' executable. By default the postmaster is taken from the same directory as pg_ctl, or failing that, the hard-wired installation directory. It is not necessary to use this option unless you are doing something unusual and get errors that the postmaster was not found. __-s__ Only print errors, no informational messages. __-w__ Wait for the start or shutdown to complete. Times out after 60 seconds. This is the default for shutdowns. __-W__ Do not wait for start or shutdown to complete. This is the default for starts and restarts. __FILES__ If the file ''postmaster.opts.default'' exists in the data directory, the contents of the file will be passed as options to the __postmaster__, unless overridden by the __-o__ option. !!EXAMPLES __STARTING THE POSTMASTER__ To start up a __postmaster__: $ __pg_ctl start __An example of starting the __postmaster__, blocking until the postmaster comes up is: $ __pg_ctl -w start __For a __postmaster__ using port 5433, and running without __fsync__, use: $ __pg_ctl -o __ __STOPPING THE POSTMASTER__ $ __pg_ctl stop __stops the postmaster. Using the __-m__ switch allows one to control __how__ the backend shuts down. __RESTARTING THE POSTMASTER__ This is almost equivalent to stopping the __postmaster__ and starting it again except that pg_ctl saves and reuses the command line options that were passed to the previously running instance. To restart the __postmaster__ in the simplest form: $ __pg_ctl restart __To restart __postmaster__, waiting for it to shut down and to come up: $ __pg_ctl -w restart __To restart using port 5433 and disabling fsync after restarting: $ __pg_ctl -o __ __SHOWING POSTMASTER STATUS__ Here is a sample status output from __pg_ctl__: $ __pg_ctl status __pg_ctl: postmaster is running (pid: 13718) Command line was: /usr/local/pgsql/bin/postmaster '-D' '/usr/local/pgsql/data' '-p' '5433' '-B' '128' This is the command line that would be invoked in restart mode. !!BUGS Waiting for complete start is not a well-defined operation and may fail if access control is set up so that a local client cannot connect without manual interaction. It should be avoided. !!SEE ALSO postmaster(1), ''PostgreSQL Administrator's Guide'' ----
2 pages link to
pg_ctl(1)
:
postmaster(1)
Man1p
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
