Dear Tom,
ISTM that the core business of a database is to help organize and protect data, and it is plainly that. You just wish you won't need it, so it is somehow "abstract", but when and if you need it, it is not "second-order" at all;-) and it is much too late to redo the dump.
So you create some tablespaces by hand. Big deal.
I agree that is is doable this way, although not really nice.
This objection is not strong enough to justify an ugly, klugy definition for where tables get created.
I do also agree about this.
My real point is that while reading the thread quickly, I was afraid the problem would not be better addressed at all in the coming release.
It seems that I was wrong as it does not look to be the case. Any fix instead of nothing is fair enough for me.
Thanks for your answer, have a nice day,
-- Fabien Coelho - [EMAIL PROTECTED]
---------------------------(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
