Ask Ubuntu is a question and answer site for Ubuntu users and developers. 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

I've got a new installation and I'm trying to get Postgresql working.

The database was installed and I started a restoration from a dump on another machine, but that ran into problems because I had forgotten to install the "contrib" package. I used "pg_dropcluster" to drop the old cluster so I could start from scratch, and that's when things went weird.

The first manifestation of this was that /etc/postgresql was just empty. I uninstalled the postgresql package and reinstalled, several times, to no avail.

Is there something I can do to figure out why apt is confused here? I've done this many times on many systems and never seen anything like this happen.

share|improve this question
up vote 5 down vote accepted

OK, I purged it, as well as the "common" package, and it's better now.

Seems like it'd be kind-of nice if it wouldn't get hosed like that.

edit that is:

  • apt-get purge postgresql postgresql-common postgresql-9.1 postgresql-contrib-9.1
  • apt-get -f install
  • apt-get autoremove
  • apt-get install postgresql postgresql-common postgresql-9.1 postgresql-contrib-9.1

and then it worked.

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.