Postgresql – How to completely remove EnterpriseDB Installation of Postgresql on Ubuntu

enterprisedbpostgresqlpostgresql-9.3Ubuntu

All,

I'm trying to install/run PostgreSQL 9.3, but am receiving a multitude of errors which seem to point to a failed installation of postgresql from the enterpriseDB package.

For example, trying to start the server with this command:

sudo /etc/init.d/postgresql-9.3 restart (or start)

…yields the following:

Restarting PostgreSQL 9.3: 
-su: /opt/PostgreSQL/9.3/bin/pg_ctl: No such file or directory
PostgreSQL 9.3 did not start in a timely fashion, please see /opt/PostgreSQL/9.3/data/pg_log/startup.log for details

Except there is no /opt/PostgreSQL/ folder, and I've been told that creation of that was attempted during the EnterpriseDB installation…why the start command is trying to go there, I do not know!

I've started another thread which gave me a very temporary solution, but that doesn't seem to help after I do a restart of my machine.

So the question, how do I completely remove the EnterpriseDB failed installation?

I've tried these commands, but the issue still lingers:

sudo apt-get autoremove postgresql-9.3-postgis pgadmin3
sudo apt-get --purge remove postgresql\*

Any thoughts or recommendations are welcome!

Thank you!

-m

Best Answer

In Feb 2009, Scahin_S wrote in [1] to use the uninstall-postgresql binary. In the same thread Sachin_S also documented a manual alternative for uninstalling 8.3 is

/opt/PostgreSQL/8.3/installer/server/removeshortcuts.sh /opt/PostgreSQL/8.3 8.3 
/etc/init.d postgresql-8.3 stop 
rm -rf /opt/PostgreSQL 
rm /etc/postgres-reg.ini 
rm -rf /etc/init.d/postgresql-8.3 
userdel postgres 

if /etc/ld.so.conf exists, edit it and remove /opt/PostgreSQL/8.3/lib 
if present. 

if /etc/ld.so.conf.d exists: 

rm /etc/ld.so.conf.d/postgresql-8.3.conf

1 - "Uninstall Postgres" thread Enterprise DB "PostgreSQL Installers for Windows, Linux and OS X" forum http://forums.enterprisedb.com/posts/list/1437.page

Related Solutions

PostgreSQL on Ubuntu – Using conf files for recovery

The recovery.conf file needs to go into the data directory (/var/lib/postgresql/...). The other configuration files can stay where they are (/etc/postgresql/...). Then a normal restart should do what you want.

Postgresql – pg_upgrade unrecognized configuration parameter “unix_socket_directory”

I hacked the problem by running (as root):

mv /usr/bin/pg_ctl{,-orig}
echo '#!/bin/bash' > /usr/bin/pg_ctl
echo '"$0"-orig "${@/unix_socket_directory/unix_socket_directories}"' >> \
     /usr/bin/pg_ctl
chmod +x /usr/bin/pg_ctl

Run pg_upgrade as intended, then undo the hack:

    mv -f /usr/bin/pg_ctl{-orig,}

The problem is that pg_upgrade executes the program pg_ctrl with arguments that specify files in the old "unix_socket_directory" rather than the new "unix_socket_directories" (note the second is plural). This hack renames the original /usr/bin/pg_ctl to /usr/bin/pg_ctl-orig, and then creates a shell script in its place that simply calls the original pg_ctl program, passing all arguments with any strings "unix_socket_directory" changed to "unix_socket_directories".

In bash, one can change a portion of a string, say from bar to baz in a variable $foo, by using ${foo/bar/baz} (note this does not change the variable, but rather returns the variable's modified contents). Arrays can also be used with ${x/y/z} to retrieve an array with all of its contents replaced, all at once. The variable $@ is an array that contains all arguments passed to the program/script/function, so the new pg_ctl script executes the old one with all arguments changed from the old directory name to the new one.

Best Answer

Related Solutions

PostgreSQL on Ubuntu – Using conf files for recovery

Postgresql – pg_upgrade unrecognized configuration parameter “unix_socket_directory”

Related Question