pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: Trenta sis <trenta.sis@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Massive update, memory usage
Date: Thu, 28 Oct 2010 07:24:33 +0800
Message-ID: <4CC8B4B1.1070208@postnewspapers.com.au> (raw)
In-Reply-To: <AANLkTiniK=6ZLjiQJYHnRSO_zsePYjqGf=cm733JG+3R@mail.gmail.com>
References: <AANLkTimt5WsyiXZFqNkFRWK330JxUEy-288qaS2KX+9f@mail.gmail.com>
	<AANLkTiniK=6ZLjiQJYHnRSO_zsePYjqGf=cm733JG+3R@mail.gmail.com>

On 10/28/2010 02:38 AM, Trenta sis wrote:
>
> Hi,
>
> I have a Linux Server (Debian) with Postgres 8.3 and I have problems
> with a massive update, about 400000 updates/inserts.
> If I execute about 100000 it seems all ok, but when I execute 400000, I
> have the same problem with or without a transaction (I need to do with a
> transaction) increase memory usage and disk usage.
> With a execution of 400.000 inserts/update server begin woring well, but
> after 100 seconds of executions increase usage of RAM, and then Swap and
> finally all RAM and swap are used and execution can't finish.

Do you have lots of triggers on the table? Or foreign key relationships 
that're DEFERRABLE ?

--
Craig Ringer



view thread (7+ messages)  latest in thread

Message-ID: <4CC8B4B1.1070208@postnewspapers.com.au>
Permalink:  ../4CC8B4B1.1070208@postnewspapers.com.au/
Also on:    postgresql.org/message-id/4CC8B4B1.1070208@postnewspapers.com.au

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, trenta.sis@gmail.com
  Subject: Re: Massive update, memory usage
  In-Reply-To: <4CC8B4B1.1070208@postnewspapers.com.au>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox