Casey Duncan wrote:
>
> I was speaking from and end-user point of view, but I see your point.
> It's certainly attractive to just patch libpq and be done. However,
> that does have the side-effect of implicitly propagating the behavior
> to all libpg client software. That may be more unpleasantly
> surprising to more people then just changing the built-in postgresql
> client utilities. But then again it could also be considered a
> feature 8^)
We change libpq from time to time. Besides, how many DBs are there that
match the name pattern /^conn:.*=/ ? My guess is mighty few. So I don't
expect lots of surprise.
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
