Tom, Pavel,
> > Hmm, I see your point. I'm personally satisfied with adding a new
> > proargmode to solve this as you suggest.
>
> This will break client-side code that looks at proargmode, and I don't
> think the argument in favor is strong enough to justify that ...
What kind of client-side code are we talking about breaking? Just pgAdmin &
phpPgAdmin and the like, or potentially other stuff that calls stored
procedures?
FWIW, pgAdmin3 1.6 *already* breaks on 8.3 procedures, so we have client-side
breakage already.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
---------------------------(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
