| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Odd out of memory problem. |
| Date: | 2012-03-26 16:59:05 |
| Message-ID: | 4F70A059.5070601@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26.03.2012 19:51, Greg Stark wrote:
> On Mon, Mar 26, 2012 at 5:41 PM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> Combo CIDs: 755490840 total in 100 blocks; 5161072 free (381
>> chunks); 750329768 used
>
> I think you'll have to catch Heikki's attention to get a good answer to this.
>
> 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?
.. and all that in different subtransactions.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2012-03-26 17:01:21 | Re: Odd out of memory problem. |
| Previous Message | Simon Riggs | 2012-03-26 16:57:57 | Re: Odd out of memory problem. |