Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 9E4379FB344 for ; Tue, 22 May 2007 03:29:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 21905-04 for ; Tue, 22 May 2007 03:29:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mxfep04.bredband.com (mxfep04.bredband.com [195.54.107.79]) by postgresql.org (Postfix) with ESMTP id 6C4C79FB354 for ; Tue, 22 May 2007 03:29:09 -0300 (ADT) Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep04.bredband.com with ESMTP id <20070522062906.KBUI24095.mxfep04.bredband.com@ironport2.bredband.com> for ; Tue, 22 May 2007 08:29:06 +0200 Received: from c-5416e555.03-51-73746f3.cust.bredbandsbolaget.se (HELO scode.mine.nu) ([85.229.22.84]) by ironport2.bredband.com with ESMTP; 22 May 2007 08:29:06 +0200 Received: from scode.mine.nu (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id 9150DC59A; Tue, 22 May 2007 08:29:06 +0200 (CEST) Message-ID: <46528DA9.1000406@infidyne.com> Date: Tue, 22 May 2007 08:28:57 +0200 From: Peter Schuller User-Agent: Thunderbird 2.0.0.0 (X11/20070501) MIME-Version: 1.0 To: PFC CC: Andreas Kostyrka , Arjen van der Meijden , pgsql-performance@postgresql.org Subject: Re: Postgres Benchmark Results References: In-Reply-To: X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig99E131892F82DF208404C452" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/417 X-Sequence-Number: 24807 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig99E131892F82DF208404C452 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > - Deferred Transactions, since adding a comment to a blog post > doesn't need the same guarantees than submitting a paid order, it makes= > sense that the application could tell postgres which transactions we > care about if power is lost. This will massively boost performance for > websites I believe. This would be massively useful. Very often all I care about is that the transaction is semantically committed; that is, that other transactions starting from that moment will see the modifications done. As opposed to actually persisting data to disk. In particular I have a situation where I attempt to utilize available hardware by using concurrency. The problem is that I have to either hugely complicate my client code or COMMIT more often than I would like in order to satisfy dependencies between different transactions. If a deferred/delayed commit were possible I could get all the performance benefit without the code complexity, and with no penalty (because in this case persistence is not important). --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --------------enig99E131892F82DF208404C452 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGUo2xDNor2+l1i30RCFt0AKDsSxj7WIhaMJEbdI4EwR6scrlSfgCfcqk4 IN+L0JCMGUhaWG3x3HdM06c= =TeMG -----END PGP SIGNATURE----- --------------enig99E131892F82DF208404C452--