On Wed, 11 Feb 2004, David Teran wrote:
> Hi,
>
> > Is your int_value data type int4? If not then use "... from
> > job_property
> > where int_value = '0'"
> > Indexes are used only if datatypes matches.
> >
> tried those variations already. Strange enough, after dropping and
> recreating the i
Oops! [EMAIL PROTECTED] (Pavel Stehule) was seen spray-painting on a wall:
>
> Regards
> Pavel Stehule
>
> On Wed, 11 Feb 2004, David Teran wrote:
>
>> Hi
>>
>> we have a table with about 4 million rows. One column has an int value,
>> there is a btree index on it. We tried to execute the followi
Had you done a VACUUM ANALYZE at all? There has been much discussion
lately about the planner needing to be updated to know that the index
is a better choice.
On Feb 11, 2004, at 6:32 AM, David Teran wrote:
Hi,
Is your int_value data type int4? If not then use "... from
job_property
where in
Hi,
Is your int_value data type int4? If not then use "... from
job_property
where int_value = '0'"
Indexes are used only if datatypes matches.
tried those variations already. Strange enough, after dropping and
recreating the index everything worked fine.
regards David
---
>
> Hi
>
> we have a table with about 4 million rows. One column has an int value,
> there is a btree index on it. We tried to execute the following
> statement and it is very slow on a dual G5 2GHZ with 4 GB of RAM.
>
> explain analyze select count(*) from job_property where int_value = 0;
>
> Ag
Hello,
If you has index on id, then you can use
SELECT id FROM tabulka ORDER BY id DESC LIMIT 1;
See 4.8. FAQ
Regards
Pavel Stehule
On Wed, 11 Feb 2004, David Teran wrote:
> Hi
>
> we have a table with about 4 million rows. One column has an int value,
> there is a btree index on it. We t
Hi
we have a table with about 4 million rows. One column has an int value,
there is a btree index on it. We tried to execute the following
statement and it is very slow on a dual G5 2GHZ with 4 GB of RAM.
explain analyze select count(*) from job_property where int_value = 0;
Aggregate (cost=1
