Re: version problem with pg_dump

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: version problem with pg_dump
Date: 2006-03-23 22:47:51
Message-ID: 44232597.2040905@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>My quick-n-dirty "fix" is to make symbolic links in /usr/bin for all pg
>>programs:

But, as I noted, only after you are sure you have removed all vestiges
of the old version. The symbolic links are just a convenience.

> The *right* solution if you're using an RPM-based Linux distro is to
> grab an RPM distribution of Postgres; trying to make end runs around RPM
> is a great way to turn your system into a hopeless mess.

You sure can turn a system into a hopeless mess but I don't agree that I
would only use RPM to install PG - that depends on the situation.

In my case the distros may use RPM as the package manager and RPM is
fine for the base configuration but I am starting with the bare minimum
default installation, hardening/stripping that down some more and then
compiling PG from source. The server has one purpose - running
PostgreSQL as a stand-alone server for clients on the network. Because
of this there are no PG dependent packages installed to start with.

PG is critical to our business and I find that compiling from source
gives me the ability to deploy updates more quickly if necessary and to
customize the options I use to build PG where necessary.

Cheers,
Steve

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Crawford 2006-03-23 23:02:54 Build only clients
Previous Message David Fetter 2006-03-23 22:46:51 Re: [GENERAL] COPY command documentation