On Fri, Jul 31, 2009 at 3:02 AM, Daniel Verite <daniel@xxxxxxxxxxxxxxxx> wrote:
Jennifer Trey wrote:Actually you should restrain from doing that, because it would break the
> >> locate pg_config
> /opt/PostgreSQL/8.4/bin/pg_config
> /opt/PostgreSQL/8.4/include/ecpg_config.h
> /opt/PostgreSQL/8.4/include/pg_config.h
> /opt/PostgreSQL/8.4/include/pg_config_manual.h
> /opt/PostgreSQL/8.4/include/pg_config_os.h
> /opt/PostgreSQL/8.4/include/postgresql/server/pg_config.h
> /opt/PostgreSQL/8.4/include/postgresql/server/pg_config_manual.h
> /opt/PostgreSQL/8.4/include/postgresql/server/pg_config_os.h
> /opt/PostgreSQL/8.4/share/man/man1/pg_config.1
> /usr/bin/pg_config
> /usr/share/man/man1/pg_config.1.gz
> >> echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>
> I am guessing I should delete the pg_config (or else there would be a
> conflict, right?) in the /usr/bin
package that installed that file, and then your system would become harder to
manage in the long run. It's better to act at the package level with the dpkg
command.
/usr/bin/pg_config is part of the libpq-dev package (this can be found with
dpkg -S /usr/bin/pg_config)
Probably you haven't uninstalled this package, which you can check by
running:
dpkg -s libpq-dev (look at the Status field). In this case, remove it
(apt-get remove libpq-dev)
Thanks.Yes, it was still there. I un-installed it.
Should I still add the pg_config to the $PATH ?
>> export PATH=/opt/PostgreSQL/8.4/bin/:$PATH
You can also remove the postgresql-common and postgresql-client-8.3 packages
if they're still there and you want to avoid any possible conflict with your
other postgresql installation.
dpkg -l 'postgresql*' also displays the list of most PG-related packages and
whether they're installed or not.
root@Ubuntu-904-jaunty-64-minimal:~# dpkg -l 'postgresql*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==========================-==========================-====================================================================
pn postgresql <none> (no description available)
un postgresql-7.4 <none> (no description available)
un postgresql-8.0 <none> (no description available)
rc postgresql-8.3 8.3.7-1 object-relational SQL database, version 8.3 server
pn postgresql-client <none> (no description available)
pn postgresql-client-8.3 <none> (no description available)
pn postgresql-client-common <none> (no description available)
rc postgresql-common 97 PostgreSQL database-cluster manager
un postgresql-dev <none> (no description available)
un postgresql-doc-8.3 <none> (no description available)
Looks fine?
It doesn't look like the uninstallation of the server itself has gone bad in
> Is there other things that could have been destroyed by the bad
> un-installment other than pg_config or was that it ?
any way. You mentioned removing the package without stopping the server
beforehand, but personally I doubt that the package uninstall process doesn't
do it automatically.
Ok, that's good to hear. I must have missed un-installing the package mentioned above.
What I did was to uninstall the postgresql-common which then removed some other depending packages.I am not sure how this package got installed.
Best regards,
--
Daniel
PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org
Sincerely / Jennifer
