Re: BUG #4204: COPY to table with FK has memory leak

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #4204: COPY to table with FK has memory leak
Date: 2008-05-28 18:22:36
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-hackers

[moving to -hackers]

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "Tomasz Rybak" <bogomips(at)post(dot)pl> writes:
>> I tried to use COPY to import 27M rows to table:
>> CREATE TABLE sputnik.ccc24 (
>> station CHARACTER(4) NOT NULL REFERENCES sputnik.station24 (id),
>> ) INHERITS (sputnik.sputnik);
>> COPY sputnik.ccc24(id, moment, station, strength, sequence, flags)
>> FROM '/tmp/24c3' WITH DELIMITER AS ' ';
> This is expected to take lots of memory because each row-requiring-check
> generates an entry in the pending trigger event list. Even if you had
> not exhausted memory, the actual execution of the retail checks would
> have taken an unreasonable amount of time. The recommended way to do
> this sort of thing is to add the REFERENCES constraint *after* you load
> all the data; that'll be a lot faster in most cases because the checks
> are done "in bulk" using a JOIN rather than one-at-a-time.

Hm, it occurs to me that we could still do a join against the pending event
trigger list... I wonder how feasible it would be to store the pending trigger
event list in a temporary table instead of in ram.

Gregory Stark
Ask me about EnterpriseDB's On-Demand Production Tuning

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-05-28 20:28:27 Re: BUG #4204: COPY to table with FK has memory leak
Previous Message Martin Drescher 2008-05-28 16:56:28 BUG #4206: function xpath gives wrong results

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2008-05-28 20:13:31 Re: Packages in oracle Style
Previous Message Gregory Stark 2008-05-28 17:55:27 Re: Avoiding second heap scan in VACUUM