I have postgresql 8.4 installed on my desktop. It keeps starting on bootup because I think I used default settings.

so I issue /etc/init.d/postgresql stop everytime and sometimes i keep forgetting

It has folder paths as,


There are a lot of configuration files and if someone can tell me where to look and what to change, that will be great.



This can help you: http://www.linuxquestions.org/questions/linux-general-1/how-to-remove-postgresql-from-startup-481963/#post2417585

But install chkconfig first:

sudo apt-get install chkconfig

and then use it

| improve this answer | |

On Ubuntu 16.04 or later (which use systemd) you'd use this command

sudo systemctl disable postgresql

If you want to re-enable, you'd do

sudo systemctl enable postgresql

On Ubuntu 15.10 and older, you can use update-rc.d:

janus@Zeus:~$ sudo update-rc.d -f postgresql remove
 Removing any system startup links for /etc/init.d/postgresql ...
| improve this answer | |
  • 1
    this is the proper way to do what was requested – glarrain Nov 11 '13 at 14:55

Using update-rc.d is better but you can do it with chkconfig:

sudo apt-get install chkconfig
sudo chkconfig -s  postgresql off

In Ubuntu 12.04, you also need to create a symlink to insserv's location:

sudo ln -s /usr/lib/insserv/insserv /sbin/insserv
| improve this answer | |
  • I had to create the symlink using 10.10 as well. In addition I got this large output as a response: pastebin.com/fPKRj5Gr – vemv Dec 27 '12 at 20:52

The answers in here are outdated. Take a look at Daniel Vérité's answer on Preventing PostgreSQL from starting on boot in Ubuntu - Database Administrators Stack Exchange.

Ubuntu or Debian can run multiple instances of PostgreSQL and provide a specific way to autostart/stop/start each cluster.

There should be a file named start.conf inside /etc/postgresql/9.2/main (or more generally /etc/postgresql/<version>/<clustername>) with these self-explanatory contents:

# Automatic startup configuration
# auto: automatically start/stop the cluster in the init script
# manual: do not start/stop in init scripts, but allow manual startup with
#         pg_ctlcluster
# disabled: do not allow manual startup with pg_ctlcluster (this can be easily
#           circumvented and is only meant to be a small protection for
#           accidents).


If you replace auto by manual, you could start this PostgreSQL instance only when desired with the command:

sudo pg_ctlcluster 9.2 main start

As for looking at the console, what you should want instead is having this run in a terminal when you work with the database:

tail -f /var/log/postgresql/postgresql-9.2-main.log
| improve this answer | |
  • Please don't post link-only answers to other Stack Exchange questions. Instead, include the essential portions of the answer here, and tailor the answer to this specific question. – double-beep Jun 11 '19 at 15:39

On my server there is another effect:

# update-rc.d -f postgresql remove
update-rc.d: using dependency based boot sequencing

No system startup links were removed.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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