pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Patches (PostgreSQL) <pgsql-patches@postgresql.org>
Subject: Re: [HACKERS] 8.2 features?
Date: Sat, 29 Jul 2006 21:27:20 -0400
Message-ID: <21320.1154222840@sss.pgh.pa.us> (raw)
In-Reply-To: <44CB051D.6090609@joeconway.com>
References: <200607281947.k6SJlOI02533@momjian.us>
	<473.1154116455@sss.pgh.pa.us>
	<44CA76A9.8070101@joeconway.com>
	<44CB051D.6090609@joeconway.com>

Joe Conway <mail@joeconway.com> writes:
>> I'm afraid though that after 2 or so days heading down the last path you 
>> suggested (namely making a new jointree leaf node) I was having trouble, 
>> and at the same time came to the conclusion that adding a new RTE was 
>> alot cleaner and made more sense to me. So I'm hoping you won't want to 
>> send me back to the drawing board again. I believe I have cleaned up the 
>> things you objected to:

I was just objecting to having both a new RTE type and a new jointree
node type --- you only need one or the other.  Opting for the new RTE
type is fine with me, and it probably is a bit cleaner at the end of
the day.

I still dislike the way you're doing things in the executor though.
I don't see the point of using the execScan.c machinery; most of the
time that'll be useless overhead.  As I said before, I think the right
direction here is to split Result into two single-purpose node types
and make the non-filter version capable of taking a list of targetlists.

As far as reducing memory use goes, it seems to me that there's no need
for the individual "targetlists" to have ResTarget/TargetEntry
decoration.  For the simple case where the expressions are just Const
nodes, this could save something like a third of the space (there's also
a List node per item, which we can't do much about).  I think we'd have
to gin up a fake targetlist to attach to the Plan node, but there'd be
only one.

Since the result-node split is my hot button, I'm willing to volunteer
to make it happen.  Do you want to concentrate on the remaining
parser-area issues and leave the executor part to me?

			regards, tom lane



view thread (56+ messages)  latest in thread

Message-ID: <21320.1154222840@sss.pgh.pa.us>
Permalink:  ../21320.1154222840@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21320.1154222840@sss.pgh.pa.us

 · 

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-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mail@joeconway.com, pgsql-patches@postgresql.org
  Subject: Re: [HACKERS] 8.2 features?
  In-Reply-To: <21320.1154222840@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