That was the short form exhibiting the bug. Selecting the complex column from a table into a value results in the same error.
BEGIN; CREATE TYPE timestamp_with_precision AS ( timestamp timestamp with time zone , timestamp_precision varchar ); CREATE TABLE timetest(t timestamp_with_precision); INSERT INTO timetest VALUES ((CURRENT_DATE, 'day')::timestamp_with_precision); CREATE OR REPLACE FUNCTION testfunc() RETURNS boolean AS $FUNC$ DECLARE v_time timestamp_with_precision; BEGIN SELECT t INTO v_time FROM timetest; RETURN true; END; $FUNC$ LANGUAGE plpgsql VOLATILE SECURITY DEFINER RETURNS NULL ON NULL INPUT; SELECT testfunc(); ROLLBACK; On Sat, Nov 22, 2008 at 1:37 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Rod Taylor" <[EMAIL PROTECTED]> writes: >> DECLARE >> v_time timestamp_with_precision; >> BEGIN >> SELECT (CURRENT_DATE, 'day')::timestamp_with_precision >> INTO v_time; > > You're overthinking the problem, it should just read > > SELECT CURRENT_DATE, 'day' > INTO v_time; > > regards, tom lane > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
