From: | Jean-Michel Pouré <jm(at)poure(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: PostgreSQL does CAST implicitely between int and adomain derived from int |
Date: | 2009-08-27 14:14:39 |
Message-ID: | 1251382479.11260.29.camel@acer |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Le jeudi 27 août 2009 à 09:01 -0500, Kevin Grittner a écrit :
> The type is always put in there so that you can see what it's doing;
> it doesn't reflect anything which is actually taking any time.
My query plan for the same query is:
"Aggregate (cost=12.75..12.76 rows=1 width=0) (actual time=0.094..0.094
rows=1 loops=1)"
" -> Index Scan using t2_pkey on t2 (cost=0.00..12.25 rows=200
width=0) (actual time=0.016..0.068 rows=201 loops=1)"
" Index Cond: ((c1 >= 200) AND (c1 <= 400))"
"Total runtime: 0.142 ms"
So I don't see any :: in my results.
In my various query plans on my database, the :: is only displayed when
comparing int and int_unsigned. So I interpreted the :: as a cast.
Are you sure that :: does not inform of a cast? Do we have documentation
about that?
Kind regards,
Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-08-27 14:16:17 | Re: PostgreSQL does CAST implicitely between int and adomain derived from int |
Previous Message | Kevin Grittner | 2009-08-27 14:01:26 | Re: PostgreSQL does CAST implicitely between int and adomain derived from int |