From: Zalman Stern <zalman@netcom.com>
To: pgsql-sql@postgreSQL.org
Subject: Create table doesn't always respect atomicity of transactions.
Date: Mon, 21 Jun 1999 22:21:48 -0700 (PDT)
Message-ID: <199906220521.WAA27197@netcom15.netcom.com> (raw)
Off and on, I've been seeing a situation where the following code:
begin;
create table foo (name text);
abort; leaves a file called "foo" in the database directory and
further attempts to create a relation called foo or to select anything from
it all fail. The database has been left in an inconsistent state.
I filed a bug report on this earlier today as it seemed dead on repeatable.
But then I recompiled with debug symbols to have a go at figuring out what
was up and the problem went away. So I recompiled with full optimization
again and the problem still doesn't occur now. I've been starting over each
time with a fresh database so if it was some property of the database
itself, then that state is lost. But this is not the first time I've seen
this. Has any one else seen such a thing? Its rather troublesome 'cause when
it does happen, the database is somewhat unuseable until I remove the file
in question and I hate going in and removing files that are supposed to be
under Postgres' control...
Glancing at the code, I'm wondering if it is possible for a database to get
stuck in "bootstrap mode." It looks like that would cause problems with
transactions not properly unlink'ing files. Though I haven't scoped out the
details of that...
-Z-
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: zalman@netcom.com
Subject: Re: Create table doesn't always respect atomicity of transactions.
In-Reply-To: <199906220521.WAA27197@netcom15.netcom.com>
References: <199906220521.WAA27197@netcom15.netcom.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