"Neil D'Souza" <neil.xavier.dsouza@xxxxxxxxx> writes: > Thank you for the quick reply. The example I constructed was > specifically for this post. I modified the function as below and it > works fine now. It would be great if the point you mentioned was a > note in the PGSQL Documentation (or did I miss it). As of 9.0, plpgsql's default behavior is to throw an error when there's an ambiguity of this sort. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
