From: Damien Dougan <damien.dougan@mobilecohesion.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Very Poor Insert Performance
Date: Wed, 29 Oct 2003 14:40:06 +0000
Message-ID: <200310291440.06450.damien.dougan@mobilecohesion.com> (raw)
In-Reply-To: <3667.1067437399@sss.pgh.pa.us>
References: <200310271626.52839.damien.dougan@mobilecohesion.com>
<200310291022.24035.damien.dougan@mobilecohesion.com>
<3667.1067437399@sss.pgh.pa.us>
On Wednesday 29 October 2003 2:23 pm, Tom Lane wrote:
> Your initial message stated plainly that the problem was in INSERTs;
> it's not surprising that you got unhelpful advice.
But perhaps my use of the term "insert" to describe upload was a very bad call
given the domain of the list...
I assure you I wasn't setting out to deceive anyone! The only location i used
INSERT (ie as a Postgres keyword) was towards the end of my mail when I tried
to highlight the fact we couldn't use COPY to upload our data because of the
difficulty in maintaining the code to generate inter-table relations ahead of
time.
The problem was showing itself during database upload - so I assumed (ASS out
of U and ME and all that!) that the write delay was very large (hence the
disappointing improvements by switching off fsync etc). It was only after
further investigation that we discovered that simulated INSERTs were going
fine, but the Read delays between INSERTs where holding us up.
> Your LEFT JOINs are constraining the join order --- see
> http://www.postgresql.org/docs/7.3/static/explicit-joins.html
> You'll need to reorder the joins into something that does what you want.
Thanks very much for the heads-up, we'll reorder the joins into something more
effecient!
Damien
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: damien.dougan@mobilecohesion.com, tgl@sss.pgh.pa.us
Subject: Re: Very Poor Insert Performance
In-Reply-To: <200310291440.06450.damien.dougan@mobilecohesion.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