On Tue, Aug 17, 2010 at 11:30 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I wrote: >> Maybe so, but the parser is expected to put out a representation that >> will still be valid when the command is executed some time later. > > Rereading this, I see I didn't make my point very clearly. The reason > this code doesn't belong in parser/ is that there's no prospect the > parser itself would ever use it. ObjectAddress is an execution-time > creature because we don't want utility statement representations to be > resolved to OID-level detail before they execute.
Well, that is a good reason for doing it your way, but I'm slightly fuzzy on why we need a crisp separation between parse-time and execution-time. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
