Re: BUG #1229: memory leak in backend with COPY and FOREIGN

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Andreas Heiduk <Andreas(dot)Heiduk(at)web(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1229: memory leak in backend with COPY and FOREIGN
Date: 2004-08-24 17:25:32
Message-ID: 20040824102222.Q51878@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On Tue, 24 Aug 2004, PostgreSQL Bugs List wrote:

> I'm trying to COPY ~18Mrows into a table which has a foreign key to another
> table. Memory and swap are exhausted and finaly the postgres.log says:

This is very possibly the space taken up by the trigger queue (which
cannot currently spill out to disk). If you load a smaller number of rows
does the space go up and then down after the copy ends?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Reini Urban 2004-08-24 18:33:20 8.0.0b1 cygwin problems
Previous Message PostgreSQL Bugs List 2004-08-24 16:41:04 BUG #1229: memory leak in backend with COPY and FOREIGN KEY