Joseph Shraibman [EMAIL PROTECTED] writes:
Neil Conway wrote:
PostgreSQL ( 7.5) won't consider using an indexscan when the predicate
involves an integer literal and the column datatype is int2 or int8.
Is this fixed for 7.5? It isn't checked off on the TODO list at
Tom Lane wrote:
: * JDBC
With JDBC out of the core, I'm not sure why we still have a JDBC section
in the core TODO.
Speaking of which why is the jdbc site so hard to find? For that matter
the new foundry can only be found through the news article on the front
page.
Hello for all!
I have PostgreSQL 7.4 under last version of Cygwin and have some
problems with performance :( It is very strange... I don't remember
this problem on previous version Cygwin and PostgreSQL 7.3
I have only two simple tables:
CREATE TABLE public.files_t
(
id int8 NOT NULL,
Eugeny Balakhonov wrote:
I tries to run simple query:
select * from files_t where parent =
Use this instead:
select * from files_t where parent = '';
(parent = ::int8 would work as well.)
PostgreSQL ( 7.5) won't consider using an indexscan when the predicate
involves an integer
Try using
select * from files_t where parent = ::int8
You have declared parent as int8, but the query will assume int4 for and may not
use the index.
Also make sure you have ANALYZEd this table.
Regards,
Gary.
On 20 May 2004 at 0:07, Eugeny Balakhonov wrote:
Hello for
Neil Conway wrote:
PostgreSQL ( 7.5) won't consider using an indexscan when the predicate
involves an integer literal and the column datatype is int2 or int8.
Is this fixed for 7.5? It isn't checked off on the TODO list at
http://developer.postgresql.org/todo.php
---(end
