On Mon, 3 May 2004 14:17:11 -0400, Vikram Kulkarni
<vkulkarn@brownforces.org> wrote:
>the end of results/stats.out is:
>-- let stats collector catch up
>SELECT sleep('0:0:2'::interval);
>
>everything up till and including that matches expected/stats.out... but
>the test simply stalls there. Unless I manuall kill the process, the
>postmaster simply keeps soaking up CPU time indefinately.
Please try this interactively in a psql session:
CREATE FUNCTION sleep(interval) RETURNS integer AS '
DECLARE
endtime timestamp;
BEGIN
endtime := timeofday()::timestamp + $1;
WHILE timeofday()::timestamp < endtime LOOP
END LOOP;
RETURN 0;
END;
' LANGUAGE 'plpgsql';
SELECT timeofday();
SELECT timeofday()::timestamp;
-- wait a few seconds ...
SELECT timeofday()::timestamp;
SELECT timeofday()::timestamp + '0:0:2'::interval;
SELECT sleep('0:0:2'::interval);
... and tell us what happens.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
