| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Query with "like" is really slow |
| Date: | 2007-09-07 15:14:48 |
| Message-ID: | 20070907151448.GH6167@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Carlo Stonebanks wrote:
> <<Actually it's quite possible that
> that extra overhead in nested loop is largely gettimeofday() calls for the
> explain analyze. Does the query take less time run without explain analyze
> than it does run with it?
>>>
>
> Do you mean that an EXPLAIN ANALYZE that runs longer than the actual query
> is a symptom of time being lost to a function call?
It means that measuring alters the reality.
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"I must say, I am absolutely impressed with what pgsql's implementation of
VALUES allows me to do. It's kind of ridiculous how much "work" goes away in
my code. Too bad I can't do this at work (Oracle 8/9)." (Tom Allison)
http://archives.postgresql.org/pgsql-general/2007-06/msg00016.php
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2007-09-07 15:22:06 | Re: What's the difference between SET STORAGE MAIN and EXTENDED? |
| Previous Message | Bill Moran | 2007-09-07 15:12:16 | Re: Security Advances in Postgresql over other RDBMS |