Search Postgresql Archives

Re: Cursors and Transactions, why?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



<wespvp@syntegra.com> writes:
> On 4/6/04 3:55 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>> In theory at least, that should not be any faster than a WITH HOLD
>> cursor, since you're effectively replicating the same functionality
>> outside the database ...

> Except for the "out of memory" thing...

What "out of memory thing"?  The tuplestore code is perfectly capable of
spilling to disk --- in fact the usual performance gripe against it has
to do with spilling too soon, because sort_mem is set too small.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux