Tom,
> Personally I'd vote for *not* having any such dangerous semantics as
> that. We should have learned better by now from plpgsql experience.
> I think the best idea is to throw error for ambiguous references,
> period.
As a likely heavy user of this feature, I agree with Tom here. I really don't want the column being silently preferred
inSQL functions, when PL/pgSQL functions are throwing an error. I'd end up spending hours debugging this.
Also, I don't understand why this would be a dump/reload issue if $1 and $2 continue to work.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
San Francisco
