Re: Odd out of memory problem.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Greg Stark <stark@mit.edu>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-03-26T17:34:52Z
Lists: pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes: > On 03/26/2012 01:06 PM, Heikki Linnakangas wrote: >>> Is it possible this job is inserting and then updating (or deleteing) >>> the row it just inserted and doing a large number of such >>> insert/update operations all within the same transaction? Or perhaps >>> it's updating the same row over and over again? > It's all in a single transaction. In fact the solution I'm currently > testing and seems to be working involves breaking it up into batches of > a few thousand LOs restored per batch. Hm. The test case is just a straight pg_restore of lots and lots of LOs? What pg_dump version was the dump made with? regards, tom lane