From: Tobias Brox <tobias@nordicbet.com>
To: Kjell Tore Fossbakk <kjelltore@gmail.com>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Querying 19million records very slowly
Date: Wed, 22 Jun 2005 16:39:21 +0800
Message-ID: <20050622083921.GZ7839@tobias> (raw)
In-Reply-To: <e79986c5050622011828dd4b41@mail.gmail.com>
References: <e79986c505062112094f579a9b@mail.gmail.com>
<42B8719A.6040809@refractions.net>
<op.ssqot4d4th1vuj@localhost>
<e79986c505062200457fe97695@mail.gmail.com>
<20050622080357.GW7839@tobias>
<e79986c5050622011828dd4b41@mail.gmail.com>
[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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tobias@nordicbet.com, kjelltore@gmail.com
Subject: Re: Querying 19million records very slowly
In-Reply-To: <20050622083921.GZ7839@tobias>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox