From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | Peter <peter(at)greatnowhere(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Query optimization problem |
Date: | 2007-02-03 18:49:54 |
Message-ID: | 200702031849540000@1768825143 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> ------- Original Message -------
> From: Peter <peter(at)greatnowhere(dot)com>
> To: pgsql-general(at)postgresql(dot)org
> Sent: 03/02/07, 10:58:08
> Subject: Re: [GENERAL] Query optimization problem
>
> >>> Try SELECT count(*) FROM ... instead and see if the times are closer.
> >
> >> Correct. That executes in 300ms flat:
> >
> > So your problem is data transfer, not the query per se.
>
> Well, based on PgAdmin times I suspected some sort of heavy 'data
> preparation before it's sent out' overhead
> >
> > How old a pgAdmin are you using?
>
> 1.4.3
>
> I tried 1.5 but it was too slow rendering results from SELECT queries...
> maybe it's fixed by now
1.5 was development code - it could have been broken in any number of ways. Get 1.6.2 - it has redesigned grid rendering code which eliminates rendering time from the equation.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | brian | 2007-02-03 20:50:40 | Re: some ports closed in Fedora |
Previous Message | Joshua D. Drake | 2007-02-03 17:46:13 | Re: PG Email Client |