Re: BUG #1229: memory leak in backend with COPY and FOREIGN - Mailing list pgsql-bugs

From Stephan Szabo
Subject Re: BUG #1229: memory leak in backend with COPY and FOREIGN
Date
Msg-id 20040824102222.Q51878@megazone.bigpanda.com
Whole thread Raw
In response to BUG #1229: memory leak in backend with COPY and FOREIGN KEY  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
List 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?

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1229: memory leak in backend with COPY and FOREIGN KEY
Next
From: "Thomas Wegner"
Date:
Subject: pg_dumpall win32: could not translate host name "abc.def.de" to address: Unknown host