[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: [BUGS] Memory error
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2009-08-27 20:22:33
Message-ID: 25553.1251404553 () sss ! pgh ! pa ! us
[Download RAW message or body]

Daniel Weinberger <daniel.weinberger@gmail.com> writes:
> Yesterday I ran an SQL import.  It failed after 3.33 hours with following
> message:
> ERROR:  out of memory

Looks like the memory consumption is here:

>     AfterTriggerEvents: 317710336 total in 49 blocks; 1312 free (42 chunks);
> 317709024 used

Perhaps you should look into the memory limits on your postmaster, as
falling over after 300MB doesn't seem very sane for any reasonably
modern machine.  However, the real answer is probably to drop whatever
after-row triggers you've got on the target table (perhaps FOREIGN KEY
constraints?) and re-establish the constraints after doing the import.

There's been some speculation about better ways to manage mass updates
of foreign key constraints, but nobody's done anything about it yet...

			regards, tom lane

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[prev in list] [next in list] [prev in thread] [next in thread]