| From: | Tobias Brox <tobias(at)nordicbet(dot)com> |
|---|---|
| To: | Kjell Tore Fossbakk <kjelltore(at)gmail(dot)com> |
| Cc: | Michael Glaesemann <grzm(at)myrealbox(dot)com>, Tobias Brox <tobias(at)nordicbet(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Querying 19million records very slowly |
| Date: | 2005-06-22 09:36:44 |
| Message-ID: | 20050622093644.GA7839@tobias |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
[Kjell Tore Fossbakk - Wed at 11:10:42AM +0200]
> Which one does Pg read fastes? Does he convert datetime in the table,
> then my where clause and check, for each row? How does he compare a
> datetime with a datetime? Timestamp are easy, large number bigger than
> another large number..
>
> time (datetime) > '2005-06-21 10:36:22+02'
>
> or
>
> time (timestamp) > 'some timestamp pointing to yesterday'
If I have understood it correctly, the planner will recognize the timestamp
and compare it with the statistics in the first example but not in the
second, and thus it will be more likely to use index scan on the first one
and seqscan on the second.
--
Tobias Brox, +86-13521622905
Nordicbet, IT dept
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2005-06-22 10:53:20 | Re: Forums & tsearch2 - best practices reg. concurrency |
| Previous Message | Markus Wollny | 2005-06-22 09:14:56 | Forums & tsearch2 - best practices reg. concurrency |