Re: joining two tables slow due to sequential scan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Tim Jones" <TJones@xxxxxxxxx>
Subject: Re: joining two tables slow due to sequential scan
From: Tom Lane <tgl@xxxxxxxxxxxxx>
Date: Fri, 10 Feb 2006 17:51:50 -0500
Cc: "Scott Marlowe" <smarlowe@xxxxxxxxxxxxxxxxx>, "Dave Dutcher" <dave@xxxxxxxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx
Comments: In-reply-to "Tim Jones" <TJones@xxxxxxxxx> message dated "Fri, 10 Feb 2006 17:43:58 -0500"
In-reply-to: <47668A1334CDBF46927C1A0DFEB223D313131D@xxxxxxxxxxxxxxxxxxxxxx>
References: <47668A1334CDBF46927C1A0DFEB223D313131D@xxxxxxxxxxxxxxxxxxxxxx>

"Tim Jones" <TJones@xxxxxxxxx> writes:
> QUERY PLAN
> 'Hash Join  (cost=899.83..4384.17 rows=482 width=1350) (actual
> time=0.203..0.203 rows=0 loops=1)'
> ...
> 'Total runtime: 0.392 ms'

Hardly seems like evidence of a performance problem ...

			regards, tom lane

References:
- Re: joining two tables slow due to sequential scan
  - From: Tim Jones

Prev by Date: Re: joining two tables slow due to sequential scan
Next by Date: Re: joining two tables slow due to sequential scan
Previous by thread: Re: joining two tables slow due to sequential scan
Next by thread: Re: joining two tables slow due to sequential scan
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux