mirror of
https://git.postgresql.org/git/postgresql.git
synced 2026-02-24 07:17:00 +08:00
9a86f03b4e
This is a second try at what commit 57431a911 tried to do, namely, launch the syslogger before we open postmaster sockets so that our messages about the sockets end up in the syslogger files. That commit fell foul of a bunch of subtle issues caused by trying to launch a postmaster child process before creating shared memory. Rather than messing with that interaction, let's postpone opening the sockets till after we launch the syslogger. This would not have been terribly safe before commit 7de19fbc0, because we relied on socket opening to detect whether any competing postmasters were using the same port number. But now that we choose IPC keys without regard to the port number, there's no interaction to worry about. Also delay creation of the external PID file (if requested) till after the sockets are open, since external code could plausibly be relying on that ordering of events. And postpone most of the work of RemovePgTempFiles() so that that potentially-slow processing still happens after we make the external PID file. We have to be a bit careful about that last though: as noted in the discussion subsequent to bug #15804, EXEC_BACKEND builds still have to clear the parameter-file temp dir before launching the syslogger. Patch by me; thanks to Michael Paquier for review/testing. Discussion: https://postgr.es/m/15804-3721117bf40fb654@postgresql.org
57 lines
2.1 KiB
C
57 lines
2.1 KiB
C
/*-------------------------------------------------------------------------
|
|
*
|
|
* pidfile.h
|
|
* Declarations describing the data directory lock file (postmaster.pid)
|
|
*
|
|
* Portions Copyright (c) 1996-2019, PostgreSQL Global Development Group
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
*
|
|
* src/include/utils/pidfile.h
|
|
*
|
|
*-------------------------------------------------------------------------
|
|
*/
|
|
#ifndef UTILS_PIDFILE_H
|
|
#define UTILS_PIDFILE_H
|
|
|
|
/*
|
|
* As of Postgres 10, the contents of the data-directory lock file are:
|
|
*
|
|
* line #
|
|
* 1 postmaster PID (or negative of a standalone backend's PID)
|
|
* 2 data directory path
|
|
* 3 postmaster start timestamp (time_t representation)
|
|
* 4 port number
|
|
* 5 first Unix socket directory path (empty if none)
|
|
* 6 first listen_address (IP address or "*"; empty if no TCP port)
|
|
* 7 shared memory key (empty on Windows)
|
|
* 8 postmaster status (see values below)
|
|
*
|
|
* Lines 6 and up are added via AddToDataDirLockFile() after initial file
|
|
* creation; also, line 5 is initially empty and is changed after the first
|
|
* Unix socket is opened. Onlookers should not assume that lines 4 and up
|
|
* are filled in any particular order.
|
|
*
|
|
* Socket lock file(s), if used, have the same contents as lines 1-5, with
|
|
* line 5 being their own directory.
|
|
*/
|
|
#define LOCK_FILE_LINE_PID 1
|
|
#define LOCK_FILE_LINE_DATA_DIR 2
|
|
#define LOCK_FILE_LINE_START_TIME 3
|
|
#define LOCK_FILE_LINE_PORT 4
|
|
#define LOCK_FILE_LINE_SOCKET_DIR 5
|
|
#define LOCK_FILE_LINE_LISTEN_ADDR 6
|
|
#define LOCK_FILE_LINE_SHMEM_KEY 7
|
|
#define LOCK_FILE_LINE_PM_STATUS 8
|
|
|
|
/*
|
|
* The PM_STATUS line may contain one of these values. All these strings
|
|
* must be the same length, per comments for AddToDataDirLockFile().
|
|
* We pad with spaces as needed to make that true.
|
|
*/
|
|
#define PM_STATUS_STARTING "starting" /* still starting up */
|
|
#define PM_STATUS_STOPPING "stopping" /* in shutdown sequence */
|
|
#define PM_STATUS_READY "ready " /* ready for connections */
|
|
#define PM_STATUS_STANDBY "standby " /* up, won't accept connections */
|
|
|
|
#endif /* UTILS_PIDFILE_H */
|