diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-10-21 20:22:38 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-10-21 20:22:38 +0000 |
| commit | 289e2905c82fc37f8b82b088bb823742aad4bb68 (patch) | |
| tree | 5b6b6ffdcac66e9cd657be0f49d91893c816f448 /src/backend/parser/parse_target.c | |
| parent | e1c96527c78bb47e1530a0f12d4f54777ef84d90 (diff) | |
| download | postgresql-289e2905c82fc37f8b82b088bb823742aad4bb68.tar.gz postgresql-289e2905c82fc37f8b82b088bb823742aad4bb68.zip | |
Remove add_missing_from GUC and associated parser support for "implicit RTEs".
Per recent discussion, add_missing_from has been deprecated for long enough to
consider removing, and it's getting in the way of planned parser refactoring.
The system now always behaves as though add_missing_from were OFF.
Diffstat (limited to 'src/backend/parser/parse_target.c')
| -rw-r--r-- | src/backend/parser/parse_target.c | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/src/backend/parser/parse_target.c b/src/backend/parser/parse_target.c index 1635c74ae1d..3aff83955b8 100644 --- a/src/backend/parser/parse_target.c +++ b/src/backend/parser/parse_target.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/parser/parse_target.c,v 1.172 2009/07/16 06:33:43 petere Exp $ + * $PostgreSQL: pgsql/src/backend/parser/parse_target.c,v 1.173 2009/10/21 20:22:38 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -927,9 +927,8 @@ ExpandColumnRefStar(ParseState *pstate, ColumnRef *cref, rte = refnameRangeTblEntry(pstate, schemaname, relname, cref->location, &sublevels_up); if (rte == NULL) - rte = addImplicitRTE(pstate, - makeRangeVar(schemaname, relname, - cref->location)); + errorMissingRTE(pstate, + makeRangeVar(schemaname, relname, cref->location)); rtindex = RTERangeTablePosn(pstate, rte, &sublevels_up); @@ -973,8 +972,7 @@ ExpandColumnRefStar(ParseState *pstate, ColumnRef *cref, * * tlist entries are generated for each relation appearing in the query's * varnamespace. We do not consider relnamespace because that would include - * input tables of aliasless JOINs, NEW/OLD pseudo-entries, implicit RTEs, - * etc. + * input tables of aliasless JOINs, NEW/OLD pseudo-entries, etc. * * The referenced relations/columns are marked as requiring SELECT access. */ |