Phoenix Kiula wrote:
Table "public.users"
Column |Type |
Modifiers
---+-+--
modify_date | timestamp without time zone |
On Monday 12 January 2009 10:18:59 Phoenix Kiula wrote:
> > When queries used to be fast and now are slow very often depends upon the
> > indexes. Less frequently upon the amount of memory available for cache
> > and the server configuration.
> > Do you used ti have any index on that column?
> > Do
> When queries used to be fast and now are slow very often depends upon the
> indexes. Less frequently upon the amount of memory available for cache and
> the server configuration.
> Do you used ti have any index on that column?
> Do you have server configuration files for comparison?
The config
On Monday 12 January 2009 09:40:22 Phoenix Kiula wrote:
> 2009/1/12 Thomas Markus :
> Thanks. But it used to work without this, and more importantly, this
> doesn't explain why the ">" queries are so exceedingly slow now! Any
> thoughts?
When queries used to be fast and now are slow very often de
check explain analyze
tried this on 8.3 with real life data:
-- all rows, index useless
explain analyze select id from cl_customer where modified > '2008-01-01'
Seq Scan on cl_customer (cost=0.00..38958.79 rows=1448639 width=8)
(actual time=0.030..682.940 rows=1448783 loops=1)
Filter: (modi
2009/1/12 Thomas Markus :
> be sure to use correct data types. I suppose psql uses timestamps so
>
> select id from users where modify_date = '2009-01-08' limit 1;
>
> is converted to
>
> select id from users where modify_date = '2009-01-08 00:00:00'::timestamp
> limit 1;
>
>
> try
>
> select id fr
be sure to use correct data types. I suppose psql uses timestamps so
select id from users where modify_date = '2009-01-08' limit 1;
is converted to
select id from users where modify_date = '2009-01-08 00:00:00'::timestamp limit
1;
try
select id from users where modify_date::date = '2009-01-
