Re: [PERFORM] not using indexes on large table

2007-04-26 Thread Scott Marlowe
On Sat, 2007-04-21 at 15:17, Jeroen Kleijer wrote: > Hi all, > > I'm a bit new to PostgreSQL and database design in general so forgive me > for asking stupid questions. ;-) > > I've setup a PostgreSQL database on a Linux machine (2 processor, 1GB > mem) and while the database itself resides on a

Re: [PERFORM] not using indexes on large table

2007-04-23 Thread Dave Dutcher
> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Jeroen Kleijer > > The problems comes when I try to do a query without using a > where clause > because by then, it completely discards the indexes and does > a complete > table scan which takes over half an hour! (40.710.725

Re: [PERFORM] not using indexes on large table

2007-04-21 Thread Andreas Kostyrka
* Jeroen Kleijer <[EMAIL PROTECTED]> [070421 23:10]: > > Hi all, > > I'm a bit new to PostgreSQL and database design in general so forgive me > for asking stupid questions. ;-) > > I've setup a PostgreSQL database on a Linux machine (2 processor, 1GB > mem) and while the database itself resides

Re: [PERFORM] not using indexes on large table

2007-04-21 Thread Vincenzo Romano
On Saturday 21 April 2007 22:17:42 Jeroen Kleijer wrote: > I've tried several things but doing a query like: > select distinct volume from project_access_times I'm new too but an "order by volume" could help! In any case maybe a different table design with a separate table for the "distinct volu

[PERFORM] not using indexes on large table

2007-04-21 Thread Jeroen Kleijer
Hi all, I'm a bit new to PostgreSQL and database design in general so forgive me for asking stupid questions. ;-) I've setup a PostgreSQL database on a Linux machine (2 processor, 1GB mem) and while the database itself resides on a NetApp filer, via NFS, this doesn't seem to impact the performan