From: | Tomasz Myrta <jasiek(at)lamer(dot)pl> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | dynamic-static date |
Date: | 2001-09-12 12:22:18 |
Message-ID: | 3B9F537A.9230A1@lamer.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
I have something like this:
billy=# EXPLAIN SELECT * from kursy where id_trasy=1 and
data_kursu=date('2001-12-12');
NOTICE: QUERY PLAN:
Index Scan using pp on kursy (cost=0.00..51.55 rows=1 width=18)
billy=# EXPLAIN SELECT * from kursy where id_trasy=1
and data_kursu='2001-12-12';
NOTICE: QUERY PLAN:
Index Scan using pp on kursy (cost=0.00..2.02 rows=1 width=18)
Why the first expression is 25 times slower?
I suppose, that planner thinks, that date('2001-12-12') is a dynamic
variable - is it true? I found this problem when i had to add date and
integer. Little "iscachable" function helped me, but I still don't know
why it happened.
CREATE FUNCTION date_sum(date,integer) returns date AS'
BEGIN
return $1+$2;
END;
'LANGUAGE 'plpgsql' WITH (iscachable);
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2001-09-12 15:17:39 | Bug #449: there is a problem with foreign key |
Previous Message | pie yves | 2001-09-12 10:28:19 | problem with foreign key |
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2001-09-12 12:29:27 | Re: backend hba.c prob |
Previous Message | Peter Eisentraut | 2001-09-12 12:07:40 | Re: syslog by default? |