Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For PostgreSQL 8.3 and later, what are the processes that make up the server and that respond to a query?

What signals do the various processes respond to and what effect do the signals have?

What are the guidelines for which signals should or shouldn't be sent and when they should or shouldn't be used?

share|improve this question
up vote 2 down vote accepted

Older versions of Postgres used signals for more things. I'm writing about the newly-released 8.4 here, and it also applies to 8.3. If you're looking for info on an older version, update your question accordingly.

Postgres 8.3's "postmaster" will terminate when receiving signals SIGTERM, SIGINT, and SIGQUIT. Like any process, you can kill it with SIGKILL, but that causes an unclean shutdown and can damage the database so it should be avoided. You shouldn't go shooting SIGQUITs at postmaster processes, either, because that can be interpreted as a crash by child postmaster processes. You really should be using pg_ctl to start / stop postmaster, though.

SIGHUP causes postmaster to re-read its configuration files (as is typical with a lot of Unix-style apps). You'd have to SIGHUP every running postmaster process if you want them all to re-read their configuraiton files.

See for more details.

share|improve this answer
+1, info added to wiki. – Avery Payne Jul 6 '09 at 23:25

Check the "Notes" section in any version of the manual in the chapter for the postgres server application. Here's the link for 8.3.x:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.