Ok, that did it. All fixed up and upgraded to 8. The command for
gentoo to rebuild WITH the pg-hier patch is (for those that might see
this question again):
# USE="pg-hier" emerge "=postgresql-7.4.7-r2" -vD # or whatever latest
7.x version is at that time.
Backup the data, etc. Then when you're done just
# emerge postgresql -vD
to update to the latest version which SHOULD NOT have the patch enabled
by default. Do another initdb and restore your data.
I'm wondering how it got there in the first place. Wonder if there was
a bad release where that flag was enabled by default. Oh well, better now.
Thanks for all the help!
G
Russell Smith wrote:
On Sat, 4 Jun 2005 09:25 am, Alvaro Herrera wrote:
On Fri, Jun 03, 2005 at 05:55:36PM -0500, Gerald D. Anderson wrote:
[snip]
I guess your build with the "use flag" wasn't successful. I think you
have two choices:
1. really build with the patch installed, and dump your data using that
Given the number of reports we have had about this specific bug on the lists.
I have take the time to submit a bug directly to the gentoo project. Hopefully
that can fit it properly and we will not see this happening again.
For reference the bug is at:
http://bugs.gentoo.org/show_bug.cgi?id=94965
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
