From: | Bob Lunney <bob_lunney(at)yahoo(dot)com> |
---|---|
To: | Tomas Vondra <tv(at)fuzzy(dot)cz>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: database slowdown while a lot of inserts occur |
Date: | 2012-04-01 02:20:03 |
Message-ID: | 1333246803.96113.YahooMailNeo@web162804.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)fuzzy(dot)cz>
To: pgsql-performance(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ofer Israeli | 2012-04-01 20:24:43 | TCP Overhead on Local Loopback |
Previous Message | Aidan Van Dyk | 2012-03-31 13:42:49 | Re: Tablespaces on a raid configuration |