From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: When do we lose column names? |
Date: | 2012-02-09 19:48:40 |
Message-ID: | 1328816728-sup-1188@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Andrew Dunstan's message of jue feb 09 16:38:27 -0300 2012:
> OK, the one place that needs to be fixed to avoid the crash caused by
> the json regression tests with the original patch is in
>
> src/backend/parser/parse_expr.c:transformRowExpr().
>
> Other candidates I have found that don't set colnames and should
> probably use dummy names are:
>
> * src/backend/parser/gram.y (row: production)
> * src/backend/optimizer/prep/prepunion.c:adjust_appendrel_attrs_mutator()
> * src/backend/optimizer/util/var.c:flatten_join_alias_vars_mutator()
>
>
> Given a function:
>
> extern List *makeDummyColnames(List * args);
>
>
> what's the best place to put it? I couldn't see a terribly obvious place
> in the source.
parse_relation.c?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-09 19:54:08 | Re: When do we lose column names? |
Previous Message | Andrew Dunstan | 2012-02-09 19:38:27 | Re: When do we lose column names? |