| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Odd out of memory problem. |
| Date: | 2012-03-26 17:34:52 |
| Message-ID: | 13875.1332783292@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-03-26 17:54:43 | Re: Odd out of memory problem. |
| Previous Message | Andrew Dunstan | 2012-03-26 17:23:58 | Re: Odd out of memory problem. |