Re: Querying 19million records very slowly - Mailing list pgsql-performance

From Tobias Brox
Subject Re: Querying 19million records very slowly
Date
Msg-id 20050622083921.GZ7839@tobias
Whole thread Raw
In response to Re: Querying 19million records very slowly  (Kjell Tore Fossbakk <kjelltore@gmail.com>)
Responses Re: Querying 19million records very slowly  (Michael Glaesemann <grzm@myrealbox.com>)
List pgsql-performance
[Kjell Tore Fossbakk - Wed at 10:18:30AM +0200]
> I'll test the use of current_timestamp, rather than now(). I am not
> sure if Pg can do a match between a fixed timestamp and a datetime?

I have almost all my experience with timestamps wo timezones, but ... isn't
that almost the same as the timedate type?

> time > current_timestamp - interval '24 hours',
> when time is yyyy-mm-dd hh-mm-ss+02, like 2005-06-22 16:00:00+02.

Try to type in '2005-06-21 16:36:22+08' directly in the query, and see if it
makes changes.  Or probably '2005-06-21 10:36:22+02' in your case ;-)

(btw, does postgresql really handles timezones?  '+02' is quite different
from 'CET', which will be obvious sometime in the late autoumn...)

--
Tobias Brox, +86-13521622905
Nordicbet, IT dept

pgsql-performance by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Configurator project launched
Next
From: Michael Glaesemann
Date:
Subject: Re: Querying 19million records very slowly