From: Neil Conway <neilc@samurai.com>
To: Jon Jensen <jon@endpoint.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Avoid MVCC using exclusive lock possible?
Date: Sun, 29 Feb 2004 09:15:57 -0500
Message-ID: <4041F41D.4050308@samurai.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402282119440.13411@louche.swelter.net>
References: <r4L_b.49293$AE3.13622@nntp-post.primus.ca>
<Pine.LNX.4.58.0402282119440.13411@louche.swelter.net>
Jon Jensen wrote:
> How would you do a rollback if an error occurred mid-query? How would you
> keep your table from being a big pile of junk if a power failure happened
> during the query?
As most non-MVCC database do: by writing WAL records.
In theory, it seems to me that we could implement an overwriting
storage manager for PostgreSQL (i.e. we'd have both MVCC and non-MVCC,
and allow users to choose at runtime). It would require a *lot* of
work, but I can't see any fundamental reason why it wouldn't be possible.
-Neil
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-hackers@postgresql.org
Cc: neilc@samurai.com, jon@endpoint.com
Subject: Re: Avoid MVCC using exclusive lock possible?
In-Reply-To: <4041F41D.4050308@samurai.com>
* 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