<wespvp@syntegra.com> writes: > On 4/6/04 11:09 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote: >> 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. > I tried doing a mass update of all rows with a single SQL statement in psql > and after it ran for many hours, I got 'out of memory'. It's unlikely that that had anything to do with tuplestores. My guess is that you had some AFTER triggers on the updated table (eg, for foreign key checks) and that what we ran out of memory for was the list of deferred trigger events. Last I checked, there was still not provision to spill that to disk when it gets big :-( regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
