From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <mha@sollentuna.net>
Cc: Markus Schaber <schabi@logix-tt.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Inserts optimization?
Date: Wed, 19 Apr 2006 11:14:52 -0400
Message-ID: <26312.1145459692@sss.pgh.pa.us> (raw)
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCEA352C3@algol.sollentuna.se>
References: <6BCB9D8A16AC4241919521715F4D8BCEA352C3@algol.sollentuna.se>
"Magnus Hagander" <mha@sollentuna.net> writes:
>>> Actually, [commit_delay] might well hurt by introducing extra delays.
>>
>> Well, if you read the documentation, you will see that it
>> will only wait if there are at least commit_siblings other
>> transactions active. So when Bacula serializes access, there
>> will be no delays, as there is only a single transaction alive.
> Hm. Right. Well, it still won't help :-)
It could actually hurt, because nonzero time is required to go look
whether there are any other active transactions. I'm not sure whether
this overhead is enough to be measurable when there's only one backend
running, but it might be.
regards, tom lane
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, mha@sollentuna.net, schabi@logix-tt.com
Subject: Re: Inserts optimization?
In-Reply-To: <26312.1145459692@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