From: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump fails |
Date: | 2005-04-19 23:06:45 |
Message-ID: | 200504200906.46240.mr-russ@pws.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 19 Apr 2005 11:53 pm, Lorenzo Thurman wrote:
> Thanks for the reply. I've tried recompiling with my install build
> settings, but no luck. I've posted a message on the Gentoo forums.
> Hopefully they will have an answer. If they do, I'll post back here for
> future reference.
>
I read your post in the forums. And as Tom suggested, it's going nothing to do with pg_dump,
you need to remerge postgresql at the very least, and with some C and USE flags you understand.
The Usual Gentoo causes come to mind first. USE flags set correctly? what are they?
What are your GCC flags. I see a lot of gentoo users who just about turn on every compiler flag
without actually knowing what they do, or how they effect things. Are your C_FLAGS conservative?
I've been using Postgresql on gentoo for both 7.4, and 8.0 from beta to 8.0.2 with no problems. But then
I always set my C_FLAGS to something conservative like CGLAGS="-march=i586 -mcpu=i586 -O2 -pipe"
yes, it may seems a "Gentoo Conservative" buy I don't get broken software. Always check extra patches
applied to the default distribution if you ever have trouble to weed out problem. And never build with and
USE flags you don't understand the implications of. Especially package specific ones.
I understand Tom's frustration, as Redhat is in business and ships quality checked software, and Gentoo
is run by a community group. Of which I think may of the packagers are not tied to the projects they are
packaging. But I also think there is often fault with the Gentoo user attempting to bleed his system a little
too much for speed, without considering the stability or even understand it.
Regards
Russell Smith.
> On Apr 19, 2005, at 1:01 AM, Tom Lane wrote:
>
> > Lorenzo Thurman <lorenzo(at)thethurmans(dot)com> writes:
> >> I'm trying that right now. I think there may be mis-match in the build
> >> settings between upgrades of postgresql. The "USE" settings may be at
> >> fault:
> >
> >> - - pg-hier : Enables recursive queries like Oracle's
> >> 'CONNECT
> >> BY' feature.
> >
> > [ rolls eyes... ] Yup, that's Gentoo all right: throw in random
> > patches
> > that have been rejected by the upstream developers. Now that I think
> > about it, this failure is exactly what that patch is known to cause,
> > because it makes an incompatible change in Query structures and hence
> > in on-disk view rule representation.
> >
> >> I think these may have been changed since the original install.
> >
> > Go back to your prior setting, or even better stop using Gentoo's
> > hacked-up version. I'm not sure why we even bother to answer support
> > requests from Gentoo users, when what they are using is not our
> > software but some randomly-modified variant. I wonder what other
> > brokennesses Gentoo may be including ...
> >
> > (Just for the record: I work for Red Hat, which has a rather different
> > notion of the level of reliability it wants to ship. So take my
> > opinion
> > with the appropriate grain of salt. But I'm a mite ticked off at the
> > moment --- you're not the first person to have been bitten by this,
> > and you likely won't be the last, and I think it's entirely because
> > Gentoo has such a low quality standard for the patches they ship.)
> >
> > regards, tom lane
> >
> >
>
>
> Tech/Library Combo Lab Manager
> Northwestern University
> Office Tech MG49
> mailto:lthurman(at)northwestern(dot)edu
> voice: 847-467-6565
> pager: 847-536-0094
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Sacks | 2005-04-20 00:39:42 | lots of puzzling log messages |
Previous Message | Baldur Norddahl | 2005-04-19 22:34:30 | postgresql start/stop/status script |