From: Greg Stark <gsstark@mit.edu>
To: Arjen van der Meijden <acmmailing@vulcanus.its.tudelft.nl>
Cc: pgsql-performance@postgresql.org
Subject: Re: Large CASE-statement is pretty slow?
Date: 15 Mar 2004 12:20:49 -0500
Message-ID: <87smga2fim.fsf@stark.xeocode.com> (raw)
In-Reply-To: <4054E8ED.3090200@vulcanus.its.tudelft.nl>
References: <4054B36C.8030306@vulcanus.its.tudelft.nl>
<25013.1079298580@sss.pgh.pa.us>
<4054E8ED.3090200@vulcanus.its.tudelft.nl>
Arjen van der Meijden <acmmailing@vulcanus.its.tudelft.nl> writes:
> Well, I have discarded this type of query as "too inefficient" and found a
> better way
Loading the mapping into a table with an index and doing an update using
"from" to do a join seems likely to end up being the most efficient method.
Postgres would probably not even bother with the index and do a hash join.
--
greg
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-performance@postgresql.org
Cc: gsstark@mit.edu, acmmailing@vulcanus.its.tudelft.nl
Subject: Re: Large CASE-statement is pretty slow?
In-Reply-To: <87smga2fim.fsf@stark.xeocode.com>
* 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