On Wed, Mar 28, 2012 at 10:39 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > The SELECT INTO tests all fail, but we know the reason why (the testbed > isn't expecting them to result in creating separate entries for the > utility statement and the underlying plannable SELECT).
This might be a dumb idea, but for a quick hack, could we just rig SELECT INTO, CREATE TABLE AS, and EXPLAIN not to create entries for themselves at all, without suppressing creation of an entry for the underlying query? The output might be slightly misleading but it wouldn't be broken, and I'm disinclined to want to spend a lot of time doing fine-tuning right now. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
