From: Bob Lunney <bob_lunney@yahoo.com>
To: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: database slowdown while a lot of inserts occur
Date: Sat, 31 Mar 2012 19:20:03 -0700 (PDT)
Message-ID: <1333246803.96113.YahooMailNeo@web162804.mail.bf1.yahoo.com> (raw)
In-Reply-To: <4F7659AC.1000507@fuzzy.cz>
References: <B75CD08C73BD3543B97E4EF3964B7D701E43F734@CITESMBX5.ad.uillinois.edu>
<B75CD08C73BD3543B97E4EF3964B7D701E440798@CITESMBX5.ad.uillinois.edu>
<1333049228.99470.YahooMailNeo@web162801.mail.bf1.yahoo.com>
<4F7659AC.1000507@fuzzy.cz>
Tomas,
You are correct. I was assuming that each insert was issued as an implicit transaction, without the benefit of an explicit BEGIN/COMMIT batching many of them together, as I've seen countless times in tight loops trying to pose as a batch insert.
Bob
________________________________
From: Tomas Vondra <tv@fuzzy.cz>
To: pgsql-performance@postgresql.org
Sent: Friday, March 30, 2012 8:11 PM
Subject: Re: [PERFORM] database slowdown while a lot of inserts occur
On 29.3.2012 21:27, Bob Lunney wrote:
> Lance,
>
> May small inserts cause frequent fsyncs. Is there any way those small
> inserts can be batched into some larger sets of inserts that use copy to
> perform the load?
Not necessarily - fsync happens at COMMIT time, not when the INSERT is
performed (unless each INSERT stands on it's own).
Tomas
--
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: bob_lunney@yahoo.com, tv@fuzzy.cz
Subject: Re: database slowdown while a lot of inserts occur
In-Reply-To: <1333246803.96113.YahooMailNeo@web162804.mail.bf1.yahoo.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