From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Joel Fradkin <jfradkin(at)wazagua(dot)com> |
Cc: | PostgreSQL Perform <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: FW: speed of querry? |
Date: | 2005-04-18 14:30:58 |
Message-ID: | 20050418072558.E7812@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, 18 Apr 2005, Joel Fradkin wrote:
> Another odd thing is when I tried turning off merge joins on the XP desktop
> It took 32 secs to run compared to the 6 secs it was taking.
> On the Linux (4proc box) it is now running in 3 secs with the mergejoins
> turned off.
>
> Unfortunately it takes over 2 minutes to actually return the 160,000+ rows.
> I am guessing that is either network (I have gig cards on a LAN) or perhaps
> the ODBC driver (using PGADMIN III to do the select).
>
> I tried to run on psql on the server but it was putting it out to more.
> If I do it and use > test.txt will it run it all out so I can get a time?
> Does it display the time anywhere like in pgadminIII?
Redirecting should turn the pager off. \timing will add a timing number
after queries. If you want to not be bothered by the pager, you can turn
if off with \pset pager off.
From | Date | Subject | |
---|---|---|---|
Next Message | Rodrigo Moreno | 2005-04-18 14:36:01 | How to improve postgres performace |
Previous Message | Dawid Kuroczko | 2005-04-18 14:19:37 | Re: immutable functions vs. join for lookups ? |