I didn't have a single problem with the upgrade. The libs seem to be
compatible.
You just might want to kill your apache, run ldconfig, then restart it.
DEJ
> -----Original Message-----
> From: Bradford L. Barrett [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, August 10, 1999 11:44 PM
> To: Jackson, DeJuan
> Cc: Vadim Mikheev; [EMAIL PROTECTED]
> Subject: RE: [ADMIN] Elapsed time in vacuum?
>
>
> > If the machines are identical distributions, libs, and layout you can
> copy
> > over the entire pgsql tree for your data rollover. You won't have any
> time
> > to test on your very loaded server before you know if something is wrong
> but
> > you might just want to keep a copy around so that two mv's will restore
> your
> > working server. Your only down time is what's needed to cp the
> directory.
> > There are some huge advantages to having a DB that actually uses
> > your file-system,
> > DEJ
>
> I agree completely :) And yes, both machines are identical systems.
> Only problem I have is the dump/restore phase on such a huge amount of
> data... but I plan on giving it a whirl this coming weekend anyway..
>
> I've been too busy putting out fires with the current setup, but I think I
> finally have them under control. For some reason, after a few months of
> our daily delete/vacuum/insert cycles, something happend to the 'blank'
> space in the tables that was causing certain vacuums to take upwards of
> 24 hours, when they normally only take 1-2. A dump/restore seems to
> have now fixed that problem. I did notice that the post dump/restore
> table sizes were approx 60% of the pre dump/restore sizes, so it does
> appear that there was something leaking somewhere... processing time
> also decreased as well, by about the same factor. Very weird :)
>
> Does anyone know if an existing apache/php combo would need to be updated
> in conjunction with the 6.4.2->6.5.x upgrade? I'd love to just have to
> worry about the postgres update, and not have to hassle with apache/php as
> well. Didn't see much mentioned in the FAQ's/Documentation related to
> that particular aspect. I'm doing some testing now on a _third_ machine
> just to test compatability, but it would be nice to hear from someone
> who has already been through the process.
>
> --
> Bradford L. Barrett [EMAIL PROTECTED]
> A free electron in a sea of neutrons DoD#1750 KD4NAW
>
> Any GUI that doesn't allow full customization - or does not
> allow you to make it operate and look like any other GUI...
> should be considerd broken. Jim Gettys, X-windows co-author
>
>
