Tom Lane-2 wrote > I kinda forgot about this bug when I went off on vacation: > http://www.postgresql.org/message-id/
> E1UnCv4-0007oF-Bo@.postgresql Just to clarify: This patch will cause both executions of the example query to fail with the "set-valued function..." error. Also, the reason the "::varchar" one did not fail was because not cast function was ever called but the "::varchar(30)" forced a function call and thus prompted the error when the second record and resultant regexp_matches expression was encountered. Thanks! David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Fixing-bug-8228-set-valued-function-called-in-context-that-cannot-accept-a-set-tp5785622p5785629.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
