Re: [HACKERS] Slow - grindingly slow - query

From: Theo Kramer <theo(at)flame(dot)co(dot)za>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Slow - grindingly slow - query
Date: 1999-11-13 09:55:38
Message-ID: 382D359A.DB093E91@flame.co.za
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> The Informix EXPLAIN results that Theo Kramer posted (a few messages
> back in this thread) are pretty interesting too. If I'm reading that
> printout right, Informix is not any smarter than we are about choosing
> the scan types for the outer and inner queries; and yet they have a much
> faster runtime for the WHERE IN query.

The informix EXPLAIN for the 'not in' query was when I did not have an
index on registrationtype (the explain appends to file sqexplain.out so I
missed it :(). Anyway here is the Informix EXPLAIN with the index on
registrationtype.

QUERY:
------
select accountdetail.domain from accountdetail where
accountdetail.domain not in (select accountmaster.domain from accountmaster)

Estimated Cost: 4510
Estimated # of Rows Returned: 58810

1) informix.accounts: SEQUENTIAL SCAN

Filters: (informix.accounts.domain != ALL <subquery> AND
informix.accounts.registrationtype != 'N' )

Subquery:
---------
Estimated Cost: 12
Estimated # of Rows Returned: 10

1) informix.accounts: INDEX PATH

(1) Index Keys: registrationtype
Lower Index Filter: informix.accounts.registrationtype = 'N'

The speed difference with or without the subquery index is neglible for
Informix.
--------
Regards
Theo

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 1999-11-13 13:36:31 Re: [HACKERS] Backend build fails in current
Previous Message Tom Lane 1999-11-13 07:53:09 Re: [HACKERS] Backend build fails in current