Hi all. Thanks for all the good advice on how to deal with the source and
the RPMs. The PostgreSQL RPM "god" has just spoken, so I think I'll be
waiting until Saturday to get the new RPMs. But I'll be saving the messages
for when the next version of PostgreSQL comes out and I can't wait for th
> > Let's compare removing the RPM's:
>
> rpm -e `rpm -qa |grep postgresql`
Nice. I like it.
> > #rpm --erase php-pgsql-3.0.15-2
>
> That's not what you're doing for your manual install...
>
> > rm -rf ~postgres/*
>
> So postgres doesn't install it's binaries in /usr/local/bin, libraries
> in
"Steve Wolfe" <[EMAIL PROTECTED]> writes:
> > Running rpm -ql on the RPMset is too much of a hassle, right? Removing
> > all traces of the RPMset is easier than removing all traces of a from-source
> > install.
>
>Really?
>
> Let's compare removing the RPM's:
rpm -e `rpm -qa |grep postgre
> On Thursday 31 May 2001 16:22, Steve Wolfe wrote:
> > something else fills up /var, PG isn't hosed. And if PG fills up it's
> > partition, other services aren't hosed.
>
> Make a partition mounted on /var/lib/pgsql. :-)
Touche!
> > Now, play some villanous music, and enter RedHat wearin
> > Unfortunately, I can't just "compile" since I need to be able to
replace my
> > current 7.0.3 installation, installed via RPMs. How do I go about this
so I
> > don't mess everything up (leftover files and such, in addition to the
> > mandatory pg_dump) ?
>
> Install the "compiled" version some
> > Now, play some villanous music, and enter RedHat wearing a black
cape,
> > with small, beedy eyes.
>
> I don't have a cape, but I do have a red hat. And blue eyes, normal
size.
I was going for the melodrama. : )
> > They insist that an OS should not touch /usr/local, and they're
> > ri
