From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Dani Oderbolz <oderbolz@ecologic.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [SQL] "SELECT IN" Still Broken in 7.4b
Date: Sun, 24 Aug 2003 17:37:14 -0400
Message-ID: <5913.1061761034@sss.pgh.pa.us> (raw)
In-Reply-To: <20030821140139.C57728-100000@megazone.bigpanda.com>
References: <20030821140139.C57728-100000@megazone.bigpanda.com>
Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> Well, if you want to be safer, I guess you could (at runtime) decide that
> the table's gotten too big and fall back to the old method if you didn't
> entirely rip it out. I'm not sure if that'd be too ugly though, but it
> would mean that you wouldn't have to worry about it returning too many
> tuples.
I did it this way --- it falls back to the old code if the TID hash
table grows to exceed SortMem. Should be noticeably faster than the
old code for reasonably-sized IN lists.
regards, tom lane
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: tgl@sss.pgh.pa.us, sszabo@megazone.bigpanda.com, oderbolz@ecologic.de, pgsql-hackers@postgresql.org
Subject: Re: [SQL] "SELECT IN" Still Broken in 7.4b
In-Reply-To: <5913.1061761034@sss.pgh.pa.us>
* 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