Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1R0g0q-0001PO-OS
	for bitcoin-development@lists.sourceforge.net;
	Mon, 05 Sep 2011 20:43:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.47 as permitted sender)
	client-ip=209.85.214.47; envelope-from=gavinandresen@gmail.com;
	helo=mail-bw0-f47.google.com; 
Received: from mail-bw0-f47.google.com ([209.85.214.47])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1R0g0p-0003fZ-R8
	for bitcoin-development@lists.sourceforge.net;
	Mon, 05 Sep 2011 20:43:24 +0000
Received: by bkbzu17 with SMTP id zu17so6753013bkb.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 05 Sep 2011 13:43:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.156.129 with SMTP id x1mr2290565bkw.254.1315255397378;
	Mon, 05 Sep 2011 13:43:17 -0700 (PDT)
Received: by 10.204.58.135 with HTTP; Mon, 5 Sep 2011 13:43:17 -0700 (PDT)
Date: Mon, 5 Sep 2011 16:43:17 -0400
Message-ID: <CABsx9T1g2p71YLeDz5mocUJTpjaKN0tKRaFQ_HcLWyKNOaT1pw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gavinandresen[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R0g0p-0003fZ-R8
Subject: [Bitcoin-development] Pull request: Optimize database writes for
	transactions with lots of TxIns.
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 05 Sep 2011 20:43:24 -0000

And I'd appreciate review/feedback on this:
  https://github.com/bitcoin/bitcoin/pull/491

Patch from ArtForz, who discovered the problem.

The problem was chaining large transactions (transactions with lots of
ins and outs) would make the berkeley db transaction log get very big,
as the dependencies (TxIns) of a transaction might be re-written
multiple times.

With this fix, each each transaction referred to by TxIns is written once.

-- 
--
Gavin Andresen