aboutsummaryrefslogtreecommitdiff
path: root/contrib/start-scripts/linux
Commit message (Collapse)AuthorAge
* 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.