Horton

Re: SQL COPY syntax extension (was: Performance on inserts)

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hannu Krosing <hannu@tm.ee>
Cc: Thomas Lockhart <lockhart@alumni.caltech.edu>, Oliver Teuber <teuber@abyss.devicen.de>, Matthew Kirkwood <matthew@hairy.beasts.org>, pgsql-hackers@postgresql.org
Date: 2000-08-28T21:05:10Z
Lists: pgsql-hackers 
Hannu Krosing <hannu@tm.ee> writes:
> What is the status of this querytree redesign ?

Waiting for 7.2 cycle, as far as I know.

> The things the new querytree should address sould be (at least ;) - 
> 2. WITH RECURSIVE

I don't think RECURSIVE is a querytree issue --- it looks like a much
bigger problem than that :-(

The things I'm concerned about fixing with querytree redesign are
	* full SQL92 joins
	* subselects in FROM
	* view bugs (grouping and aggregates in views)
	* INSERT ... SELECT bugs
	* reimplement UNION/INTERSECT/EXCEPT in a less hacky way,
	  make cases like SELECT ... UNION ... ORDER BY work.
	  Not to mention UNION etc in a subselect or in INSERT/SELECT.
	* convert WHERE x IN (subselect) to a join-like representation

These are all things that have gone unfixed for years because they're
essentially unfixable with the current single-level representation of
a query.

			regards, tom lane