pgsql: Fix GetCTEForRTE() to deal with the possibility that the RTE it's - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix GetCTEForRTE() to deal with the possibility that the RTE it's
Date
Msg-id 20081006151522.A41D87545A4@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix GetCTEForRTE() to deal with the possibility that the RTE it's given came
from a query level above the current ParseState.

Modified Files:
--------------
    pgsql/src/backend/parser:
        analyze.c (r1.380 -> r1.381)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c?r1=1.380&r2=1.381)
        parse_relation.c (r1.137 -> r1.138)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_relation.c?r1=1.137&r2=1.138)
        parse_target.c (r1.166 -> r1.167)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_target.c?r1=1.166&r2=1.167)
    pgsql/src/include/parser:
        parse_relation.h (r1.60 -> r1.61)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/parser/parse_relation.h?r1=1.60&r2=1.61)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Use fork names instead of numbers in the file names for
Next
From: hlipa@pgfoundry.org (User Hlipa)
Date:
Subject: orafce - orafce: Improve alligment correctness in pipe.c.