[vox-tech] transactions (was: Unnecessary RDBMS features)

[Henry House]

--OgqxwSJOaUobr8KG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 24, 2003 at 08:44:32PM -0700, Matt Roper wrote:
[...]
> On the other hand, if the transaction is rolled back, you simply dump
> your memory copy and there's no disk activity at all.  This is a
> well-known scheme called "optimistic concurrency control," but there are
> certainly other transaction implementations that work just as well.
> Note that there's no unnecessary disk writing -- all the working copies
> are stored in memory.

Hence the commonly observed situation in which performace in large number of
INSERTs increases when autocommit is turned off---observed in PostgreSQL and
SQLite. Without a transaction block, each row would be written to disk
individually; in a transaction block all are written at once.

--=20
Henry House
The attached file is a digital signature. See <http://romana.hajhouse.org/p=
gp>
for information.  My OpenPGP key: <http://romana.hajhouse.org/hajhouse.asc>.

--OgqxwSJOaUobr8KG
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+qShVi3lu92AVGcIRAv6oAJ9bdylBt1NZjFQzAEJfRzympgb4NACeLL0a
hMjEYPrA3xpLFLLIuFkBusk=
=1KhI
-----END PGP SIGNATURE-----

--OgqxwSJOaUobr8KG--