From: Reece Hart <reece@in-machina.com>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: query optimization differs between view and explicit
Date: Fri, 30 Jan 2004 11:27:33 -0800
Message-ID: <1075490853.16553.109.camel@tallac> (raw)
In-Reply-To: <4862.1075440407@sss.pgh.pa.us>
References: <1075422699.4062.164.camel@tallac>
<20040129171201.I35951@megazone.bigpanda.com>
<4862.1075440407@sss.pgh.pa.us>
Stephan, Tom-
Thanks. I now see that DISTINCT can't be moved within the plan as I
thought. This is exactly the thinko that I was hoping someone would
expose.
I've decided to abandon the DISTINCT clause. The view is more general
and sufficiently fast without it, and callers can always add it
themselves to achieve what I was doing in the explicit query.
I appreciate your time.
-Reece
--
Reece Hart, http://www.in-machina.com/~reece/, GPG:0x25EC91A0
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: reece@in-machina.com
Subject: Re: query optimization differs between view and explicit
In-Reply-To: <1075490853.16553.109.camel@tallac>
* 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