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

Re: pgsql: get_names_for_var didn't do recursion for

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Tom Lane <tgl(at)svr1(dot)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: get_names_for_var didn't do recursion for
Date: 2005-01-13 19:04:46
Message-ID: 20050113150427.K45642@ganymede.hub.org (view raw or flat)
Thread:
Lists: pgsql-committers
With the several backend related changes that have gone in over the past 
couple of days, are we looking at an RC6? :(

On Thu, 13 Jan 2005, Tom Lane wrote:

> Log Message:
> -----------
> get_names_for_var didn't do recursion for unnamed JOIN vars quite right;
> got it wrong when the JOIN was in an outer query level.  Per example from
> Laurie Burrow.  Also fix same issue in markTargetListOrigin.  I think the
> latter is only a latent bug since we currently don't apply markTargetListOrigin
> except at the outer level ... but should do it right anyway.
>
> Modified Files:
> --------------
>    pgsql/src/backend/parser:
>        parse_target.c (r1.128 -> r1.129)
>        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_target.c.diff?r1=1.128&r2=1.129)
>    pgsql/src/backend/utils/adt:
>        ruleutils.c (r1.187 -> r1.188)
>        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c.diff?r1=1.187&r2=1.188)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>      joining column's datatypes do not match
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org           Yahoo!: yscrappy              ICQ: 7615664

In response to

Responses

pgsql-committers by date

Next:From: Peter EisentrautDate: 2005-01-13 19:05:25
Subject: pgsql: Translation updates
Previous:From: Tom LaneDate: 2005-01-13 18:23:22
Subject: pgsql: Adjust src/tutorial Makefile so that it can use pgxs.

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