From: | Jim Nasby <jim(at)nasby(dot)net> |
---|---|
To: | lapham(at)jandr(dot)org |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Restart after power outage: createdb |
Date: | 2006-09-27 05:34:06 |
Message-ID: | B7B1E607-38F5-4274-9B0F-7C25BDB3541B@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Sep 26, 2006, at 7:06 AM, Jon Lapham wrote:
> While trying to reproduce power outage restart problem I reported
> earlier, I have found something odd when pulling the plug on a VM
> during a createdb operation.
>
> If I run...
> sleep 3; echo starting; createdb bar
> ...and power off the VM while the "createdb bar" is running.
>
> Upon restart, about 50% of the time I can reproduce the following
> error message:
>
> [lapham(at)localhost ~]$ psql bar
> psql: FATAL: database "bar" does not exist
> [lapham(at)localhost ~]$ createdb bar
> createdb: database creation failed: ERROR: could not create
> directory "base/65536": File exists
> [lapham(at)localhost ~]$ createdb bar
> CREATE DATABASE
>
> So, running "createdb bar" a second time works. This is probably
> not a bug, but I thought I'd mention it anyway as it could
> potentially cause problems for people running scripts.
Could this be a timing issue? IE: are you just issuing the first
createdb bar too soon after the database has started?
I suspect this is a bug...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-09-27 05:45:46 | Re: Transaction is read-only in auto commit mode |
Previous Message | Jim Nasby | 2006-09-27 05:32:08 | Re: pl/perl autonomous transactions question |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-09-27 05:50:57 | Re: Block B-Tree concept |
Previous Message | Jim C. Nasby | 2006-09-27 02:47:56 | Re: Block B-Tree concept |