pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gregory Stark <stark@enterprisedb.com>
To: Ehab Galal <ehabgalal123@hotmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: marking tuples
Date: Wed, 05 Dec 2007 08:44:15 +0000
Message-ID: <87odd55y5c.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <BAY138-W31C72CF9118BE1CB6BC00966D0@phx.gbl>
References: <BAY138-W31C72CF9118BE1CB6BC00966D0@phx.gbl>

"Ehab Galal" <ehabgalal123@hotmail.com> writes:

> In my algorithm, each NewJoin node may "mark" its ps_ResultTupleSlot with
> either red/green. I need that mark to flow in the pipeline so that i can
> collect them at the top aggregate.

How will you tell about the marks from different NewJoins?

I think you'll have to "project" the tuple and add a resjunk column to
indicate that flag. I don't know how you'll identify that column from other
such flag columns other NewJoin nodes have added.

You could look at the setop code in prepunion.c like intersection to see other
plans which add flag columns. In those cases though they are used by the
direct parent of the node which added it, so the planner can just mark a field
in the parent indicating which column it should look at for the flag.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's On-Demand Production Tuning



view thread (3+ messages)  latest in thread

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

 · 

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: stark@enterprisedb.com, ehabgalal123@hotmail.com
  Subject: Re: marking tuples
  In-Reply-To: <87odd55y5c.fsf@oxford.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