From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | Rachael <rulonrasp(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6256: loading small file eats all memory and crashes system |
Date: | 2011-10-15 16:49:37 |
Message-ID: | CAFaPBrSMxKZuhvFeiRdnAVuWBaOVU9gG79fm50JrPB9XWQaYfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Oct 14, 2011 at 21:43, Rachael <rulonrasp(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6256
> Logged by: Rachael
> Email address: rulonrasp(at)gmail(dot)com
> PostgreSQL version: 9.11
> Operating system: Arch Linux
> Description: loading small file eats all memory and crashes system
> Details:
>
> While attempting to import a sql file, postgres eats all my physical memory
> (4GB) and swap file space(2GB).
>
> The file itself is a series of insert statements that is 10,000 rows by 100
> columns wide. A smaller file (1000 rows) loads just fine. I'll be glad to
> provide sample files. The command I'm using is inside a perl script:
>
> print `psql $database $user < postgres.sql`;
What happens when you remove perl from the equation? Or at the very
least while doing the import have you tired looking a top or some
other tool to see where the memory is going?
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2011-10-15 19:44:51 | Re: BUG #6256: loading small file eats all memory and crashes system |
Previous Message | Rachael | 2011-10-15 03:43:34 | BUG #6256: loading small file eats all memory and crashes system |