Skip site navigation (1) Skip section navigation (2)

Re: BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "John Smith" <sodgodofall(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts.
Date: 2008-04-04 14:46:28
Message-ID: 19115.1207320388@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"John Smith" <sodgodofall(at)gmail(dot)com> writes:
> Steps to reproduce:
>  -- start with a running PG instance with WAL archiving enabled
>  -- select pg_start_backup('test');
>  -- Fill up the disk on which the data directory is present
>  -- select pg_stop_backup();
>     -- fails with: ERROR:  could not write file
> "pg_xlog/000000010000000000000000.004989E8.backup": No space left on device
>     -- at this point there is a 0-byte file
> pg_xlog/000000010000000000000000.004989E8.backup present on disk
>  -- stop and start PG
>  -- recovery fails with: FATAL:  invalid data in file
> "000000010000000000000000.004989E8.backup"
>  -- NOTE: At this point removing 000000010000000000000000.004989E8.backup
> allows PG to start successfully

What do you see as the bug here?  Seems like reasonable behavior to me.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: John SmithDate: 2008-04-04 17:47:24
Subject: Re: BUG #4089: When available disk space is low pg_stop_backup() fails, as do subsequent recovery attempts.
Previous:From: Mikael OmmaDate: 2008-04-04 12:38:22
Subject: BUG #4091: ECPG $select incompability with Informix

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group