From: Arjen van der Meijden <acmmailing@tweakers.net>
To: Michael Stone <mstone+postgres@mathom.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to determine cause of performance problem?
Date: Fri, 23 Sep 2005 13:19:55 +0200
Message-ID: <4333E4DB.4020206@tweakers.net> (raw)
In-Reply-To: <20050923110500.GX14918@mathom.us>
References: <1127458167.2475.105.camel@Panoramix>
<20050923095517.GW14918@mathom.us>
<1127470875.3524.17.camel@Panoramix>
<20050923110500.GX14918@mathom.us>
On 23-9-2005 13:05, Michael Stone wrote:
> On Fri, Sep 23, 2005 at 12:21:15PM +0200, Joost Kraaijeveld wrote:
>
> Ok, that's great, but you didn't respond to the suggestion of using COPY
> INTO instead of INSERT.
>
>> But I have no clue where to begin with determining the bottleneck (it
>> even may be a normal performance for all I know: I have no experience
>> with converting such (large) database).
>>
>> Any suggestions?
>
>
> Respond to the first suggestion?
Another suggestion:
How many indexes and constraints are on the new table?
Drop all of them and recreate them once the table is filled. Of course
that only works if you know your data will be ok (which is normal for
imports of already conforming data like database dumps of existing tables).
This will give major performance improvements, if you have indexes and
such on the new table.
Best regards,
Arjen
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: acmmailing@tweakers.net, mstone+postgres@mathom.us
Subject: Re: How to determine cause of performance problem?
In-Reply-To: <4333E4DB.4020206@tweakers.net>
* 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