Skip site navigation (1) Skip section navigation (2)

Re: Nested CASE-WHEN scoping

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Nested CASE-WHEN scoping
Date: 2011-05-30 14:21:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> I think we can work around both of those by just saving and restoring 
> the value of each Param that we set while evaluating an expression,

Huh?  That's a waste of time and effort.  Just make sure that each such
spot has its own Param number.  That's why I'm telling you to do it in
the planner, not the parser --- it is easy to assign globally-unique-
across-the-plan numbers at plan time, in fact we do it already.

> For debugging purposes, it seems like a good idea to invent a new kind 
> of Param for these, and keep them separate from PARAM_EXEC params.

I'd vote against that too.  PARAM_EXEC Params already have more than one

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2011-05-30 14:28:17
Subject: Re: Getting a bug tracker for the Postgres project
Previous:From: Kim BisgaardDate: 2011-05-30 13:56:08
Subject: Re: Getting a bug tracker for the Postgres project

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group