From: Merlin Moncure <mmoncure@gmail.com>
To: Sabin Coanda <sabin.coanda@deuromedia.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: long transaction
Date: Sun, 17 Aug 2008 20:04:53 -0400
Message-ID: <b42b73150808171704s31ba07cl57ed92fdfdcac5ed@mail.gmail.com> (raw)
In-Reply-To: <g7ttnc$1on8$1@news.hub.org>
References: <g5qd5o$1ot3$1@news.hub.org>
<120621.32315.qm@web59503.mail.ac4.yahoo.com>
<g7onk7$12sj$1@news.hub.org>
<b42b73150808111203l14df2d2dicd4350f04d64e838@mail.gmail.com>
<g7rgtr$1cc0$1@news.hub.org>
<b42b73150808120956ie421dbcl2c24d486c8793eb9@mail.gmail.com>
<g7ttnc$1on8$1@news.hub.org>
On Wed, Aug 13, 2008 at 2:07 AM, Sabin Coanda
<sabin.coanda@deuromedia.ro> wrote:
>>
>> have you considered importing to a temporary 'holding' table with
>> copy, then doing 'big' sql statements on it to check constraints, etc?
>>
>
> Yes I considered it, but the problem is the data is very tight related
> between different tables and is important to keep the import order of each
> entity into the database. With other words, the entity imprt serialization
> is mandatory. In fact the import script doesn't keep just insert but also
> delete and update for different entities. So copy is not enough. Also using
> 'big' sql statements cannot guarantee the import order.
More than likely, to solve your problem (outside of buying bigger box
or hacking fsync) is to rethink your import along the lines of what
I'm suggesting. You're welcome to give more specific details of
what/how your imports are running, in order to get more specific
advice.
merlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mmoncure@gmail.com, sabin.coanda@deuromedia.ro
Subject: Re: long transaction
In-Reply-To: <b42b73150808171704s31ba07cl57ed92fdfdcac5ed@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox