pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Dean Gibson (DB Administrator) <postgresql3@ultimeth.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: JOIN performance
Date: 21 Sep 2004 14:26:37 -0400
Message-ID: <87oejzeaw2.fsf@stark.xeocode.com> (raw)
In-Reply-To: <23901.1095728070@sss.pgh.pa.us>
References: <5.1.0.14.2.20040920121606.00a89c68@imaps.mailpen.net>
	<414F02FF.8000603@numerixtechnology.de>
	<414F02FF.8000603@numerixtechnology.de>
	<5.1.0.14.2.20040920121606.00a89c68@imaps.mailpen.net>
	<5.1.0.14.2.20040920164348.00a99868@imaps.mailpen.net>
	<23901.1095728070@sss.pgh.pa.us>


Tom Lane <tgl@sss.pgh.pa.us> writes:

> Fixing this properly is a research project, and I haven't thought of any
> quick-and-dirty hacks that aren't too ugly to consider :-(

Just thinking out loud here. Instead of trying to peek inside the CASE
couldn't the optimizer just wrap the non-strict expression in a conditional
that tests whether the row was found?


-- 
greg

view thread (12+ messages)

Message-ID: <87oejzeaw2.fsf@stark.xeocode.com>
Permalink:  ../87oejzeaw2.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87oejzeaw2.fsf@stark.xeocode.com

copy link · copy postgr.es

reply

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: gsstark@mit.edu, tgl@sss.pgh.pa.us, postgresql3@ultimeth.com
  Subject: Re: JOIN performance
  In-Reply-To: <87oejzeaw2.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