Re: Joins and full index scans...mysql vs postgres?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: ryan groth <postgres(at)cpusoftware(dot)com>
Cc: "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Joins and full index scans...mysql vs postgres?
Date: 2006-02-22 18:28:25
Message-ID: 20060222102713.Y73083@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, 22 Feb 2006, ryan groth wrote:

> Does this work:
>
> "Merge Left Join (cost=0.00..2656.36 rows=6528 width=1522) (actual
> time=0.057..123.659 rows=6528 loops=1)"
> " Merge Cond: ("outer".uid = "inner".uid)"
> " -> Merge Left Join (cost=0.00..1693.09 rows=6528 width=1264)
> (actual time=0.030..58.876 rows=6528 loops=1)"
> " Merge Cond: ("outer".uid = "inner".user_id)"
> " -> Index Scan using users_pkey on users (cost=0.00..763.81
> rows=6528 width=100) (actual time=0.016..9.446 rows=6528 loops=1)"
> " -> Index Scan using phorum_users_base_pkey on
> phorum_users_base (cost=0.00..822.92 rows=9902 width=1168) (actual
> time=0.007..15.674 rows=9845 loops=1)"
> " -> Index Scan using useraux_pkey on useraux (cost=0.00..846.40
> rows=7582 width=262) (actual time=0.007..11.935 rows=7529 loops=1)"
> "Total runtime: 127.442 ms"

Well, this implies the query took about 127 ms on the server side. Where
did the 1000 ms number come from (was that on a client, and if so, what
type)?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message ryan groth 2006-02-22 18:52:49 Re: Joins and full index scans...mysql vs postgres?
Previous Message ryan groth 2006-02-22 18:21:04 Re: Joins and full index scans...mysql vs postgres?