On Jul 26, 2005, at 8:15 AM, Chris Isaacson wrote:
I am using InnoDB with MySQL which appears to enforce true transaction
support. (http://dev.mysql.com/doc/mysql/en/innodb-overview.html) If
not, how is InnoDB "cheating"?
are you sure your tables are innodb?
chances are high unless you exp
lto:[EMAIL PROTECTED]
Sent: Tuesday, July 26, 2005 7:12 AM
To: Chris Isaacson
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] COPY insert performance
Hi Chris,
Have you considered breaking the data into multiple chunks and COPYing
each concurrently?
Also, have you ensured that
:09 PM
To: Chris Isaacson; Postgresql Performance
Subject: Re: [PERFORM] COPY insert performance
Chris Isaacson wrote:
> I need COPY via libpqxx to insert millions of rows into two tables.
> One table has roughly have as many rows and requires half the storage.
> In production, the largest tab
ork_mem to 512MB and rerun my test. I have 1G of RAM, which
is less than we'll be running in production (likely 2G).
-Original Message-
From: John A Meinel [mailto:[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 6:09 PM
To: Chris Isaacson; Postgresql Performance
Subject: Re: [PERFORM
Hi Chris,
Have you considered breaking the data into multiple chunks and COPYing
each concurrently?
Also, have you ensured that your table isn't storing OIDs?
On Mon, 25 Jul 2005, Chris Isaacson wrote:
> #---
>
> # RESOURC
Title: Re: [PERFORM] COPY insert performance
Chris,
You can try the Bizgres distribution of postgres (based on version 8.0.3), the COPY support is 30% faster as reported by OSDL (without indexes). This is due to very slow parsing within the COPY command, which is sped up using micro-optimized
Chris Isaacson wrote:
> I need COPY via libpqxx to insert millions of rows into two tables. One
> table has roughly have as many rows and requires half the storage. In
> production, the largest table will grow by ~30M rows/day. To test the
> COPY performance I split my transactions into 10,000 r
Title: Message
I need COPY via
libpqxx to insert millions of rows into two tables. One table has roughly
have as many rows and requires half the storage. In production, the
largest table will grow by ~30M rows/day. To test the COPY performance I
split my transactions into 10,000 rows. I
