Re: Reducing memory usage of insert into select operations?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: lists(at)stringsutils(dot)com
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, dev(at)archonet(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: Reducing memory usage of insert into select operations?
Date: 2008-07-18 17:00:36
Message-ID: 29468.1216400436@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Francisco Reyes" <lists(at)stringsutils(dot)com> writes:
> Given that memory grows over time I am beggining to wonder if it is some
> type of memory leak.

Are there any AFTER triggers (including foreign key constraints) on the
table being inserted into? If so the list of pending trigger events
might be your problem.

If you can get Postgres to report an actual out-of-memory error (as
opposed to crashing from OOM kill) then it should dump a memory usage
map into the postmaster log. Looking at that would be informative.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-07-18 17:03:12 Re: Initdb problem on debian mips cobalt: Bus error
Previous Message Glyn Astill 2008-07-18 16:53:09 Re: Initdb problem on debian mips cobalt: Bus error