Lists: | pgsql-hackers |
---|
From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <pavel(dot)stehule(at)gmail(dot)com>,<david(at)kineticode(dot)com> |
Cc: | <andrew(at)dunslane(dot)net>,<robertmhaas(at)gmail(dot)com>, <mike(at)mlfowler(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Initial review of xslt with no limits patch |
Date: | 2010-08-08 17:07:35 |
Message-ID: | 4C5E9E070200002500034334@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
> I didn't use a correct name - so "indexed set" is better.
How would such a thing differ from a RAM-based local temporary table?
-Kevin
From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | david(at)kineticode(dot)com, andrew(at)dunslane(dot)net, robertmhaas(at)gmail(dot)com, mike(at)mlfowler(dot)com, pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Subject: | Re: Initial review of xslt with no limits patch |
Date: | 2010-08-08 18:05:53 |
Message-ID: | AANLkTimwd2zZbd8ieY4dBB6=an47HJQqARXzr5+Ush0V@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
2010/8/8 Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>:
> Pavel Stehule wrote:
>
>> I didn't use a correct name - so "indexed set" is better.
>
> How would such a thing differ from a RAM-based local temporary table?
temporary tables are too heavy for this purposes. In SQL environment I
expecting a transactional behave from tables. It isn't necessary. Next
tables are strict structure. And it can be useless for storing a set
of parameters.
>
> -Kevin
>
>