Re: WAL does not recover gracefully from out-of-disk-space

From: "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com>
To: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: WAL does not recover gracefully from out-of-disk-space
Date: 2001-03-08 12:37:42
Message-ID: 008d01c0a7cc$9225ed60$4c79583f@sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Was the following bug already fixed ?

I was going to ask same Q.

I see that seek+write was changed to write-s in XLogFileInit
(that was induced by subj, right?), but what about problem
itself?

> > DEBUG: redo starts at (0, 21075520)
> > The Data Base System is starting up
> > DEBUG: open(logfile 0 seg 0) failed: No such file or directory
^^^^^^^^^^^^^^^
redo started in seg 1 and shouldn't try to read seg 0...

BTW, were performance tests run after seek+write --> write-s
change? Write-s were not obviously faster to me, that's why I've
used seek+write, but never tested that area -:(

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2001-03-08 12:50:15 PostgreSQL on multi-CPU systems
Previous Message Vadim Mikheev 2001-03-08 12:24:23 Re: Proposed WAL changes