Re: [SQL] Query response time

2006-08-15 Thread Scott Marlowe
On Fri, 2006-08-11 at 08:58, Jonathan Sinclair wrote: > Hi all. Thanks for your help so far. However after configuring my system > I am still getting major lag times with a couple of queries. The first, > which suffers from the '538/539'(see old email included below) bug, is > caused by running the

Re: [SQL] Query response time

2006-08-11 Thread Jonathan Sinclair
Hi all. Thanks for your help so far. However after configuring my system I am still getting major lag times with a couple of queries. The first, which suffers from the '538/539'(see old email included below) bug, is caused by running the following statement: SELECT t1.col1, SUM(test) test_col, SU

Re: [SQL] Query response time

2006-08-09 Thread Roman Neuhauser
# [EMAIL PROTECTED] / 2006-08-08 13:25:47 +0100: > I am using PostgresSQL 7.4 and having some serious performance issues. > I am using tables that only contain approx 2GB of data. > The install was performed by yum onto a RAID server using Centos. I am > sure there is something fundamentally wron

Re: [SQL] Query response time

2006-08-08 Thread Richard Broersma Jr
> I am using PostgresSQL 7.4 and having some serious performance issues. > Trawling through the archives and previous posts the only visible advice > I could see was either by running vacuum or setting the fsynch flag to > false. > > I am using tables that only contain approx 2GB of data. However

Re: [SQL] Query response time

2006-08-08 Thread Chris Mair
> I am using PostgresSQL 7.4 and having some serious performance issues. > Trawling through the archives and previous posts the only visible advice > I could see was either by running vacuum or setting the fsynch flag to > false. > > I am using tables that only contain approx 2GB of data. However

[SQL] Query response time

2006-08-08 Thread Jonathan Sinclair
Hi all, I am using PostgresSQL 7.4 and having some serious performance issues. Trawling through the archives and previous posts the only visible advice I could see was either by running vacuum or setting the fsynch flag to false. I am using tables that only contain approx 2GB of data. However pe