Skip site navigation (1) Skip section navigation (2)

Re: BUG #4533: Plpgsql complex type failure

From: "Rod Taylor" <rod(dot)taylor(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4533: Plpgsql complex type failure
Date: 2008-11-22 18:52:53
Message-ID: 751261b20811221052o4a0f07e3pfe6b944fba385ef9@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
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 <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Rod Taylor" <rod(dot)taylor(at)gmail(dot)com> 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
>

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-11-22 18:57:10
Subject: Re: BUG #4533: Plpgsql complex type failure
Previous:From: Tom LaneDate: 2008-11-22 18:37:41
Subject: Re: BUG #4533: Plpgsql complex type failure

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group