Re: pgsql: get_names_for_var didn't do recursion for
От | Marc G. Fournier |
---|---|
Тема | Re: pgsql: get_names_for_var didn't do recursion for |
Дата | |
Msg-id | 20050113150427.K45642@ganymede.hub.org обсуждение исходный текст |
Ответ на | pgsql: get_names_for_var didn't do recursion for unnamed JOIN vars quite (tgl@svr1.postgresql.org (Tom Lane)) |
Ответы |
Re: pgsql: get_names_for_var didn't do recursion for
Re: pgsql: get_names_for_var didn't do recursion for |
Список | 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@hub.org Yahoo!: yscrappy ICQ: 7615664
В списке pgsql-committers по дате отправления: