From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dani Oderbolz <oderbolz@ecologic.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [SQL] "SELECT IN" Still Broken in 7.4b
Date: Fri, 22 Aug 2003 09:40:45 +0800
Message-ID: <00f201c3684e$6b943a40$2800a8c0@mars> (raw)
References: <20030821102627.C51705-100000@megazone.bigpanda.com>
<25062.1061498540@sss.pgh.pa.us>
> I'm toying with the notion of ripping out that logic and instead
> building an in-memory hashtable of already-returned TIDs. This could
> theoretically run out of memory if the multiple indexscan returns enough
> tuples, but I think in practice that wouldn't happen because the planner
> wouldn't choose an indexscan when very large numbers of tuples are being
> selected.
>
> Comments?
Sounds kind of like a bitmap index almost..
Chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: chriskl@familyhealth.com.au, sszabo@megazone.bigpanda.com, tgl@sss.pgh.pa.us, oderbolz@ecologic.de, pgsql-hackers@postgresql.org
Subject: Re: [SQL] "SELECT IN" Still Broken in 7.4b
In-Reply-To: <00f201c3684e$6b943a40$2800a8c0@mars>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox