From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Hans Zaunere" <lists(at)zaunere(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: COPY Performance |
Date: | 2008-05-05 15:08:05 |
Message-ID: | dcc563d10805050808v5e8df481p8ceca5854aa61b26@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 5, 2008 at 9:03 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Sun, May 4, 2008 at 5:11 PM, Hans Zaunere <lists(at)zaunere(dot)com> wrote:
> > Hello,
> >
> > We're using a statement like this to dump between 500K and >5 million rows.
> >
> > COPY(SELECT SomeID FROM SomeTable WHERE SomeColumn > '0')
> > TO '/dev/shm/SomeFile.csv'
>
> Wait, are you really creating a .csv file in shared memory? Can such
> a thing even work?
>
> If you're not creating a file in /dev/shm, where is it being built?
> On the main OS drive? the battery backed cached RAID array?
OK, looked it up. you're making your .csv file in a ramdisk? If it
gets big it's gonna make the machine start swapping. i'd suggest
storing only small things in a ram disk really. Other than that, I'm
not sure what the problem is.
From | Date | Subject | |
---|---|---|---|
Next Message | Asche | 2008-05-05 15:21:16 | Re: bytea and character encoding when inserting escaped literals |
Previous Message | Lee Feigenbaum | 2008-05-05 15:07:12 | bytea and character encoding when inserting escaped literals |