POSTGRES(1)

📦 version 18.6, in opensuse-leap 16.0

✨ POSTGRES(1) ✨

PostgreSQL 18.6 Documentation — yes bestie, it's the postgres manual page, the big one, the main character of the whole server situation 💅

🌸 NAME 🌸

postgres — it's giving... PostgreSQL database server. That's her. That's the whole vibe. 👑

🦋 SYNOPSIS 🦋

postgres [option...]

💖 DESCRIPTION 💖

okay so. postgres is the PostgreSQL database server, periodt. For a client application to actually get at a database, it has to connect — over a network or locally, either one — to a running postgres instance. And then? That instance spins up a whole separate server process just to handle that connection. one connection, one process, no cap. 🫶

One postgres instance is always managing the data of exactly one database cluster. And a database cluster is a collection of databases all stored at one common file system location — that's the “data area”, bestie. ✨

Here's the slay part: you can run more than one postgres instance on the same system at the same time, no problem — as long as they use different data areas and different communication ports (more on that below 👀). But when postgres starts up it needs to know where the data area lives. That location has to be specified by the -D option or the PGDATA environment variable. There is no default. Like, none. You have to tell her. 🙈

Typically, -D or PGDATA points directly at the data area directory that initdb(1) created. There are other possible file layouts too, and those get discussed in Section 19.2 if you're feeling academic. 📚

By default postgres starts in the foreground and prints log messages to the standard error stream. Which is cute for testing, but in practical applications postgres should be started as a background process — maybe at boot time. That's the grown-up move. 🌈

🎀 Single-user mode 🎀

The postgres command can also be called in single-user mode. Her primary use for this mode is during bootstrapping by initdb(1). Sometimes people use it for debugging or disaster recovery — but real talk:

Running a single-user server is not truly suitable for debugging the server, because no realistic interprocess communication and locking will happen. Not the vibe check you think it is. 💀

When you invoke it in single-user mode from the shell, the user can enter queries and the results get printed to the screen — but in a form that's more useful for developers than end users. iykyk.

In single-user mode, the session user gets set to the user with ID 1, and implicit superuser powers are granted to this user. And here's the wild part — this user doesn't actually have to exist. 😭 So single-user mode can be used to manually recover from certain kinds of accidental damage to the system catalogs. Disaster recovery queen fr fr 🧚💜

✨ OPTIONS ✨

okay bestie so postgres takes all these command-line arguments 💖 and for the full deep-dive discussion of them you wanna go read Chapter 19. You can literally save yourself so much typing by setting up a configuration file. And some of these options (the safe ones, okay) can also be set from the connecting client in an application-dependent way so they only apply for that one session. Like, for example, if the environment variable PGOPTIONS is set, then libpq-based clients will pass that string to the server, and the server will interpret it as postgres command-line options. cute right? 🎀

🌸 General Purpose 🌸

  • -B nbuffers — sets the number of shared buffers for use by the server processes. The default value of this parameter is chosen automatically by initdb. Specifying this option is equivalent to setting the shared_buffers configuration parameter. ✨
  • -c name=value — sets a named run-time parameter. All the config parameters PostgreSQL supports are described in Chapter 19. Most of the other command-line options are lowkey just short forms of one of these parameter assignments. And -c can appear multiple times to set multiple parameters, so go off 🫶
  • -C name — prints the value of the named run-time parameter, and exits. (See the -c option above for details, bestie.) This returns values from postgresql.conf, modified by any parameters supplied in this invocation. It does not reflect parameters supplied when the cluster was started. 👑

This can be used on a running server for most parameters. However — heads up — the server must be shut down for some runtime-computed parameters (e.g., shared_memory_size, shared_memory_size_in_huge_pages, and wal_segment_size).

This option is meant for other programs that interact with a server instance, such as pg_ctl(1), to query configuration parameter values. User-facing applications should instead use SHOW or the pg_settings view. fr fr.

  • -d debug-level — sets the debug level. The higher this value is set, the more debugging output is written to the server log. Values are from 1 to 5. It is also possible to pass -d 0 for a specific session, which will prevent the server log level of the parent postgres process from being propagated to this session. 😭
  • -D datadir — specifies the file system location of the database configuration files. See Section 19.2 for details.
  • -e — sets the default date style to "European", that is DMY ordering of input date fields. This also causes the day to be printed before the month in certain date output formats. See Section 8.5 for more information. 🌸
  • -F — disables fsync calls for improved performance, at the risk of data corruption in the event of a system crash. Specifying this option is equivalent to disabling the fsync configuration parameter. Read the detailed documentation before using this! 💀
  • -h hostname — specifies the IP host name or address on which postgres is to listen for TCP/IP connections from client applications. The value can also be a comma-separated list of addresses, or * to specify listening on all available interfaces. An empty value specifies not listening on any IP addresses, in which case only Unix-domain sockets can be used to connect to the server. Defaults to listening only on localhost. Specifying this option is equivalent to setting the listen_addresses configuration parameter. ✨
  • -i — allows remote clients to connect via TCP/IP (Internet domain) connections. Without this option, only local connections are accepted. This option is equivalent to setting listen_addresses to * in postgresql.conf or via -h.
This option is deprecated since it does not allow access to the full functionality of listen_addresses. It's usually better to set listen_addresses directly. 👑
  • -k directory — specifies the directory of the Unix-domain socket on which postgres is to listen for connections from client applications. The value can also be a comma-separated list of directories. An empty value specifies not listening on any Unix-domain sockets, in which case only TCP/IP sockets can be used to connect to the server. The default value is normally /tmp, but that can be changed at build time. Specifying this option is equivalent to setting the unix_socket_directories configuration parameter. 🦋
  • -l — enables secure connections using SSL. PostgreSQL must have been compiled with support for SSL for this option to be available. For more information on using SSL, refer to Section 18.9.
  • -N max-connections — sets the maximum number of client connections that this server will accept. The default value of this parameter is chosen automatically by initdb. Specifying this option is equivalent to setting the max_connections configuration parameter. 💖
  • -p port — specifies the TCP/IP port or local Unix domain socket file extension on which postgres is to listen for connections from client applications. Defaults to the value of the PGPORT environment variable, or if PGPORT is not set, then defaults to the value established during compilation (normally 5432). If you specify a port other than the default port, then all client applications must specify the same port using either command-line options or PGPORT. 🔥
  • -s — print time information and other statistics at the end of each command. This is useful for benchmarking or for use in tuning the number of buffers.
  • -S work-mem — specifies the base amount of memory to be used by sorts and hash tables before resorting to temporary disk files. See the description of the work_mem configuration parameter in Section 19.4.1. 🌈
  • -V, --version — print the postgres version and exit. 💅
  • --name=value — sets a named run-time parameter; a shorter form of -c. ✨
  • --describe-config — this option dumps out the server's internal configuration variables, descriptions, and defaults in tab-delimited COPY format. It is designed primarily for use by administration tools. 👑
  • -?, --help — show help about postgres command line arguments, and exit. 🎀

🙈 Semi-Internal Options 🙈

The options described here are used mainly for debugging purposes, and in some cases to assist with recovery of severely damaged databases. There should be no reason to use them in a production database setup. They are listed here only for use by PostgreSQL system developers. Furthermore, these options might change or be removed in a future release without notice. 💀 so like... be careful bestie.

  • -f { s | i | o | b | t | n | m | h } — forbids the use of particular scan and join methods: s and i disable sequential and index scans respectively, o, b and t disable index-only scans, bitmap index scans, and TID scans respectively, while n, m, and h disable nested-loop, merge and hash joins respectively.

Neither sequential scans nor nested-loop joins can be disabled completely; the -fs and -fn options simply discourage the optimizer from using those plan types if it has any other alternative. 🫶

  • -O — allows the structure of system tables to be modified. This is used by initdb.
  • -P — ignore system indexes when reading system tables, but still update the indexes when modifying the tables. This is useful when recovering from damaged system indexes.
  • -t pa[rser] | pl[anner] | e[xecutor] — print timing statistics for each query relating to each of the major system modules. This option cannot be used together with the -s option. 😭
  • -T — this option is for debugging problems that cause a server process to die abnormally. The ordinary strategy in this situation is to notify all other server processes that they must terminate, by sending them SIGQUIT signals. With this option, SIGABRT will be sent instead, resulting in production of core dump files. 💀
  • -v protocol — specifies the version number of the frontend/backend protocol to be used for a particular session. This option is for internal use only.
  • -W seconds — a delay of this many seconds occurs when a new server process is started, after it conducts the authentication procedure. This is intended to give an opportunity to attach to the server process with a debugger. 🐛

🧚 Options for Single-User Mode 🧚

The following options only apply to the single-user mode (see Single-User Mode below).

  • --single — selects the single-user mode. This must be the first argument on the command line. ⭐
  • database — specifies the name of the database to be accessed. This must be the last argument on the command line. If it is omitted it defaults to the user name.
  • -E — echo all commands to standard output before executing them.
  • -j — use semicolon followed by two newlines, rather than just newline, as the command entry terminator. ✨
  • -r filename — send all server log output to filename. This option is only honored when supplied as a command-line option.

🌈 ENVIRONMENT 🌈

  • PGCLIENTENCODING — default character encoding used by clients. (The clients can override this individually.) This value can also be set in the configuration file. 💜
  • PGDATA — default data directory location.
  • PGDATESTYLE — default value of the DateStyle run-time parameter. (The use of this environment variable is deprecated.) 👑
  • PGPORT — default port number (preferably set in the configuration file).

💖 DIAGNOSTICS 💖

So like, if it fails and the error message says something about semget or shmget? Bestie, that's basically your kernel going "ma'am I do not have enough shared memory and semaphores for this" 🫠 and it probably means you need to reconfigure your kernel to provide adequate shared memory and semaphores. There's more discussion in Section 18.4 if you wanna go deep.

Not ready to do a whole kernel glow-up right now? You might be able to postpone reconfiguring your kernel by decreasing shared_buffers to reduce the shared memory consumption of PostgreSQL, and/or by reducing max_connections to reduce the semaphore consumption. Little temporary hack, she's doing her best 💅

If the failure message is suggesting that another server is already running, do not just panic — check carefully. For example, using the command:

$ ps ax | grep postgres

or

$ ps -ef | grep postgres

depending on your system. And if you are certain that no conflicting server is running, you can remove the lock file mentioned in the message and try again. (Yes, it's giving "delete the thing and hope" but it's sanctioned, ok? ✨)

A failure message indicating inability to bind to a port? That might indicate that that port is already in use by some non-PostgreSQL process. No cap, sometimes a random little guy is just sitting on your port 😭

You might also get this error if you terminate postgres and immediately restart it using the same port. In that case you must simply wait a few seconds until the operating system closes the port before trying again. Patience, queen.

And finally, you might get this error if you specify a port number that your operating system considers to be reserved. For example, many versions of Unix consider port numbers under 1024 to be "trusted" and only permit the Unix superuser to access them. So like, don't pick port 80 and be shocked, ok? 🙈

✨ NOTES ✨

The utility command pg_ctl(1) can be used to start and shut down the postgres server safely and comfortably. Use her!! She's right there!! 🎀

If at all possible, do NOT use SIGKILL to kill the main postgres server. Doing so will prevent postgres from freeing the system resources (e.g., shared memory and semaphores) that it holds before terminating. This might cause problems for starting a fresh postgres run. This is the manpage equivalent of ghosting someone mid-conversation and leaving all your stuff at their apartment 💀

To terminate the postgres server normally, the signals SIGTERM, SIGINT, or SIGQUIT can be used. Here's the vibe breakdown, because they are not the same:

  • SIGTERM — will wait for all clients to terminate before quitting. Gentle, patient, respectful 🫶
  • SIGINT — will forcefully disconnect all clients. Sudden but effective.
  • SIGQUIT — will quit immediately without proper shutdown, resulting in a recovery run during restart. Chaotic. Iconic in a bad way.

The SIGHUP signal will reload the server configuration files. It is also possible to send SIGHUP to an individual server process, but that is usually not sensible. Like, you can, but why 😭

To cancel a running query, send the SIGINT signal to the process running that command. To terminate a backend process cleanly, send SIGTERM to that process. See also pg_cancel_backend and pg_terminate_backend in Section 9.28.2 for the SQL-callable equivalents of these two actions. Same energy, but from inside SQL ✨

The postgres server uses SIGQUIT to tell subordinate server processes to terminate without normal cleanup. This signal should not be used by users. It's for the server's own internal communication, not for you, bestie. Stay in your lane 💅

It is also unwise to send SIGKILL to a server process — the main postgres process will interpret this as a crash and will force all the sibling processes to quit as part of its standard crash-recovery procedure. Sibling processes catching strays fr fr 😭

🐛 BUGS 🐛

The -- options will not work on FreeBSD or OpenBSD. Use -c instead. This is a bug in the affected operating systems; a future release of PostgreSQL will provide a workaround if this is not fixed. Not our fault, we promise, it's literally them 🌸

🌈 SINGLE-USER MODE 🌈

To start a single-user mode server, use a command like:

postgres --single -D /usr/local/pgsql/data other-options my_database

Provide the correct path to the database directory with -D, or make sure that the environment variable PGDATA is set. Also specify the name of the particular database you want to work in. Don't skip steps, she notices 👑

Normally, the single-user mode server treats newline as the command entry terminator; there is no intelligence about semicolons, as there is in psql. So like, no fancy parsing here, she's a simple girl 🎀

To continue a command across multiple lines, you must type backslash just before each newline except the last one. The backslash and adjacent newline are both dropped from the input command.

Note that this will happen even when within a string literal or comment. Yes. Even then. She does not care. 💀

But if you use the -j command line switch, a single newline does not terminate command entry; instead, the sequence semicolon-newline-newline does. That is, type a semicolon immediately followed by a completely empty line. Backslash-newline is not treated specially in this mode. Again, there is no intelligence about such a sequence appearing within a string literal or comment. Same chaos, different trigger ✨

In either input mode, if you type a semicolon that is not just before or part of a command entry terminator, it is considered a command separator. When you do type a command entry terminator, the multiple statements you've entered will be executed as a single transaction. Group project energy but it actually works 💅

To quit the session, type EOF (Control+D, usually). If you've entered any text since the last command entry terminator, then EOF will be taken as a command entry terminator, and another EOF will be needed to exit. Two taps to leave, like a double-tap on Instagram, but for exiting a database 🌸

Note that the single-user mode server does not provide sophisticated line-editing features (no command history, for example). Single-user mode also does not do any background processing, such as automatic checkpoints or replication. She's minimal, she's focused, she's not doing all that ✨

🔥 EXAMPLES 🔥

To start postgres in the background using default values, type:

$ nohup postgres >logfile 2>&1 </dev/null &

To start postgres with a specific port, e.g., 1234:

$ postgres -p 1234

To connect to this server using psql, specify this port with the -p option:

$ psql -p 1234

or set the environment variable PGPORT:

$ export PGPORT=1234
$ psql

Named run-time parameters can be set in either of these styles:

$ postgres -c work_mem=1234
$ postgres --work-mem=1234

Either form overrides whatever setting might exist for work_mem in postgresql.conf. Notice that underscores in parameter names can be written as either underscore or dash on the command line. Cute, right? Both slay 💖

Except for short-term experiments, it's probably better practice to edit the setting in postgresql.conf than to rely on a command-line switch to set a parameter. Like, the command line is for a quick vibe check, not for your whole personality, yk? 🌈

👑 SEE ALSO 👑

initdb(1), pg_ctl(1)

And that's the whole page, bestie!! You made it to the end, I'm so proud of you 🥹💖 This was PostgreSQL 18.6, dated 2026, and yes, the manual page is literally called POSTGRES(1) — go forth and run your server, you absolute icon 🌟💅

📦 where this page comes from