Magnus Hagander wrote:
I agree with getting rid of the remaining .bat files, or at least making
them one line wrappers for perl scripts, but I think it's too late in
the cycle for that now. As I explained, the reason I didn't make more
changes before was because I thought it was too late then. I did just
enough to make running the whole thing with the buildfarm client work
reliably.
Probably, yeah. Maybe we're better off just documenting that you need both
files in some cases, rather than putting in something we don't like.
Frankly, I'd rather live with more or less invisible ugliness for one
release than have to document it and put the burden on users to set up
two environments.
I don't really like the idea of shipping withb documentation that states you
should do one thing, and it won't work... It's not invisible at all. If you
follow the documentation, you can't build...
You seem to have misunderstood what I am suggesting. Of course we should
document use of buildenv.pl in addition to the hacky fix to the .bat
files. The hack is the part that would be invisible. The docs would be
visible and contain what would be our ongoing practice.
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
