From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lutz Fischer <lfischer@staffmail.ed.ac.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: problem with large inserts
Date: Thu, 13 Dec 2012 11:10:38 -0500
Message-ID: <5810.1355415038@sss.pgh.pa.us> (raw)
In-Reply-To: <50C9F63D.5040400@staffmail.ed.ac.uk>
References: <50C9F63D.5040400@staffmail.ed.ac.uk>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Lutz Fischer <lfischer@staffmail.ed.ac.uk> writes:
> I have currently some trouble with inserts into a table
> If I run only [ the select part ]
> it returns 200620 rows in 170649 ms ( thats just under 3 minutes). I
> stopped the actual insert after about 8h.
It should not take 8h to insert 200k rows on any machine made this
century. Frankly, I'm wondering if the insert is doing anything at all,
or is blocked on a lock somewhere. You say there's no concurrent
activity, but how hard did you look? Did you check that, say, the
physical disk file for the table is growing?
> I am running postgresql 9.2 on a windows 2008 R2 server with 256 GB and
> the database is on something like a raid 1+0 (actually a raid1e)
> consisting of 3x4TB disks (limit of what could easily be fitted into the
> server).
A different line of thought is that there's something seriously broken
about the raid configuration. Have you tried basic disk-speed
benchmarks? (Perhaps there's an equivalent of bonnie++ for windows.)
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: tgl@sss.pgh.pa.us, lfischer@staffmail.ed.ac.uk
Subject: Re: problem with large inserts
In-Reply-To: <5810.1355415038@sss.pgh.pa.us>
* 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