aboutsummaryrefslogtreecommitdiff
path: root/contrib/start-scripts/linux
Commit message (Collapse)AuthorAge
* Fix typo in linux startup script.Tom Lane2015-04-26
| | | | | Missed a "$" in what was meant to be a variable substitution. Careless mistake in commit f23425fa950fec3aff458de117037c9caadbc35c.
* Improve handling of OOM score adjustment in sample Linux start script.Tom Lane2014-07-01
| | | | Per a suggestion from Christoph Berg.
* Improve our mechanism for controlling the Linux out-of-memory killer.Tom Lane2014-06-18
| | | | | | | | | | | | | | | | | | Arrange for postmaster child processes to respond to two environment variables, PG_OOM_ADJUST_FILE and PG_OOM_ADJUST_VALUE, to determine whether they reset their OOM score adjustments and if so to what. This is superior to the previous design involving #ifdef's in several ways. The behavior is now available in a default build, and both ends of the adjustment --- the original adjustment of the postmaster's level and the subsequent readjustment by child processes --- can now be controlled in one place, namely the postmaster launch script. So it's no longer necessary for the launch script to act on faith that the server was compiled with the appropriate options. In addition, if someone wants to use an OOM score other than zero for the child processes, that doesn't take a recompile anymore; and we no longer have to cater separately to the two different historical kernel APIs for this adjustment. Gurjeet Singh, somewhat revised by me
* Revert "pg_ctl: Add idempotent option"Peter Eisentraut2013-04-29
| | | | | | This reverts commit 87306184580c9c49717b00d48a2f9e717f21e0a8. The behavior in certain cases is still being debated, and it's too late to solve this before beta.
* Don't try to pass -I switch to postmaster in contrib/start-scripts/linux.Tom Lane2013-04-19
| | | | | Undo thinko in commit 87306184580c9c49717b00d48a2f9e717f21e0a8. Per bug #8098 from Catherine Devlin.
* pg_ctl: Add idempotent optionPeter Eisentraut2013-04-13
| | | | | | | | | | | | | This changes the behavior of the start and stop actions to exit successfully if the server was already started or stopped. This changes the default behavior of the start action: Before, if the server was already running, it would print a message and succeed. Now, that situation will result in an error. When running in idempotent mode, no message is printed and pg_ctl exits successfully. It was considered to just make the idempotent behavior the default and only option, but pg_upgrade needs the old behavior.
* Support Linux's oom_score_adj API as well as the older oom_adj API.Tom Lane2012-06-13
| | | | | | | | | The simplest way to handle this is just to copy-and-paste the relevant code block in fork_process.c, so that's what I did. (It's possible that something more complicated would be useful to packagers who want to work with either the old or the new API; but at this point the number of such people is rapidly approaching zero, so let's just get the minimal thing done.) Update relevant documentation as well.
* Remove cvs keywords from all files.Magnus Hagander2010-09-20
|
* Update startup scripts for Linux and FreeBSD.Bruce Momjian2010-02-23
| | | | Kevin Grittner
* Add some simple support and documentation for using process-specific oom_adjTom Lane2010-01-11
| | | | | | settings to prevent the postmaster from being OOM-killed on Linux systems. Alex Hunsaker and Tom Lane
* Make it reasonably safe to use pg_ctl to start the postmaster from a boot-timeTom Lane2009-08-27
| | | | | | | | | | | | | | | | | script. To do this, have pg_ctl pass down its parent shell's PID in an environment variable PG_GRANDPARENT_PID, and teach CreateLockFile() to disregard that PID as a false match if it finds it in postmaster.pid. This allows us to cope with one level of postgres-owned shell process even with pg_ctl in the way, so it's just as safe as starting the postmaster directly. You still have to be careful about how you write the initscript though. Adjust the comments in contrib/start-scripts/ to not deprecate use of pg_ctl. Also, fix the ROTATELOGS option in the OSX script, which was indulging in exactly the sort of unsafe coding that renders this fix pointless :-(. A pipe inside the "sudo" will probably result in more than one postgres-owned process hanging around.
* Be consistent about not using ECHO_N/ECHO_C (seems unnecessary on Linux).Peter Eisentraut2006-07-13
|
* Adjust postmaster to recognize that a lockfile containing its parent's PIDTom Lane2004-10-01
| | | | | | | | must be stale. Tweak example startup scripts to not use pg_ctl but launch the postmaster directly, thereby ensuring that only the postmaster's direct parent shell will be a postgres-owned process. In combination these should fix the longstanding problem of the postmaster sometimes refusing to start during reboot because it thinks the old lockfile is not stale.
* $Header: -> $PostgreSQL Changes ...PostgreSQL Daemon2003-11-29
|
* Fix for Linux startup script.Bruce Momjian2003-07-26
| | | | Slawomir Sudnik
* Add Linux restart --- Slawomir SudnikBruce Momjian2003-06-12
| | | | Add "-l $PGLOG" for restart --- Darko Prenosil
* Patch to add comments to Linux startup script.Bruce Momjian2001-07-30
| | | | Rene Pijlman
* Pass -D option to pg_ctl because export PGDATA won't be preserved acrossPeter Eisentraut2001-04-19
| | | | | | 'su -l'. Reported by <VASQUEZ_JASON@LILLY.COM>.
* Remove outdated contrib/linux start scripts. Beat some sense intoPeter Eisentraut2001-02-08
contrib/init.d start script. Place into more aptly named directory. Maybe we could add scripts for other platforms here later.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 09:13:40 +0000