| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Ezequiel Tolnay <mail(at)etolnay(dot)com(dot)ar>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Wishlist? |
| Date: | 2005-07-21 15:12:11 |
| Message-ID: | 20050721080841.M64679@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 21 Jul 2005, Martijn van Oosterhout wrote:
> On Thu, Jul 21, 2005 at 07:10:03PM +1000, Ezequiel Tolnay wrote:
> > * Create a ROWSET variable type in plpgsql that would function like a
> > temporary but in-memory table. Support for it would have to be added for
> > plpgsql's SELECT, UPDATE and DELETE statements.
>
> How is this different from a temporary table?
I'd expect they'd scope "correctly" in cases of recursive calls and the
like. So, if the recursive call wanted its own, it wouldn't have to try to
find an unused temporary table name. Offhand, I'm not sure if that'd
really be useful in practice once temporary tables in plpgsql didn't
require one to jump through hoops, but it has some niceness.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kilian Hagemann | 2005-07-21 15:45:55 | Query planner refuses to use index |
| Previous Message | Martijn van Oosterhout | 2005-07-21 14:28:05 | Re: Wishlist? |