| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Oliver Teuber <teuber(at)abyss(dot)devicen(dot)de>, Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL COPY syntax extension (was: Performance on inserts) |
| Date: | 2000-08-28 21:05:10 |
| Message-ID: | 18647.967496710@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)tm(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-28 21:14:30 | Re: SQL COPY syntax extension (was: Performance on inserts) |
| Previous Message | Rob Browning | 2000-08-28 20:49:06 | How hard would a "no global server" version be? |