On Mon, Aug 16, 2010 at 3:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 2. I haven't done anything about moving the definition of
>> ObjectAddress elsewhere, as Alvaro suggested, because I'm not sure
>> quite where it ought to go. I still think it's a good idea, though
>> I'm not dead set on it, either. Suggestions?
>
> I think the problem is you're trying to put this into backend/parser
> which is not really the right place for it. It's an execution-time
> animal not a parse-time animal. I would put it into backend/catalog,
> perhaps named objectaddress.c, and similarly the header file would be
> objectaddress.h. Then it would be reasonable to move struct
> ObjectAddress into this header and have dependency.h #include it.
> There might be some other stuff in dependency.c that more naturally
> belongs here, too.
If this isn't parse analysis, then you and I have very different ideas
of what parse analysis is. And under this theory, what are routines
like LookupAggNameTypeNames() doing in src/backend/parser?
I'll make the rest of the changes you suggest...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
