Re: Commit every N rows in PL/pgsql

From: Len Walter <len(dot)walter(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: Commit every N rows in PL/pgsql
Date: 2010-06-03 08:00:03
Message-ID: AANLkTilqlVO2bOkNFtlil4n4P8X-wpVmlgsxIppstzU3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
>
> > ...
> > AfterTriggerEvents: 2642403328 total in 327 blocks; 10176 free (319
> > chunks); 2642393152 used
>
> And there's the problem. Evidently you have an AFTER trigger on the
> table, and the queued events for that trigger are overrunning memory.
>

That's interesting - I don't know of any triggers on this table, but it does
have a lot of foreign key constraints. Would they fall into the same
category?

--
len(dot)walter(at)gmail(dot)com skype:lenwalter
msn:len(dot)walter(at)gmail(dot)com<msn%3Alen(dot)walter(at)gmail(dot)com>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message J. Bagg 2010-06-03 09:16:11 Re: libreadline and Debian 5 - not missing just badly named
Previous Message John R Pierce 2010-06-03 06:15:56 Re: c program fails to run with the postgres which is installed at user location