From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Organization: Dynacom Tankers Mgmt
To: pgsql-admin@postgresql.org
Subject: Re: Postgresql 9.0.2 explain analyze very slow (10x),
	compared to actual query time
User-Agent: KMail/1.9.7
References: <201101111753.22602.achill@matrix.gatewaynet.com>
	<201101141553.38236.achill@matrix.gatewaynet.com>
	<4D300C2E0200002500039569@gw.wicourts.gov>
In-Reply-To: <4D300C2E0200002500039569@gw.wicourts.gov>
MIME-Version: 1.0
Content-Disposition: inline
Date: Fri, 14 Jan 2011 17:52:34 +0200
Content-Type: text/plain;
  charset="iso-8859-7"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201101141752.34986.achill@matrix.gatewaynet.com>

=D3=F4=E9=F2 Friday 14 January 2011 16:41:18 =E3=F1=DC=F8=E1=F4=E5:
> Achilleas Mantzios <achill@matrix.gatewaynet.com> wrote:
> =20
> > and NOT EXISTS=20
> >    (SELECT distinct mold.id from marinerstates
> =20
> Does that do better if you leave out the DISTINCT keyword?  Maybe
> use * instead of the column name?

Its already really fast, it doesn't matter. Anyways just tried without the =
distinct=20
=2E..NOT EXISTS (SELECT 1 from ...
and its the same (high) speed. The other form (NOT IN) is the problem (in t=
he case of postgresql-9.0.2).
(in 8.3 both queries are fast)

> =20
> -Kevin
>=20


=2D-=20
Achilleas Mantzios