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

2008-04-04 Thread John Smith 

The following bug has been logged online:

Bug reference:  4089
Logged by:  John Smith
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system:   Linux 2.6.20-gentoo-r8
Description:When available disk space is low pg_stop_backup() fails,
as do subsequent recovery attempts.
Details: 

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/0001.004989E8.backup": No space left on device
-- at this point there is a 0-byte file
pg_xlog/0001.004989E8.backup present on disk
 -- stop and start PG
 -- recovery fails with: FATAL:  invalid data in file
"0001.004989E8.backup"
 -- NOTE: At this point removing 0001.004989E8.backup
allows PG to start successfully

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [PATCHES] Re: [BUGS] BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data

2008-04-04 Thread Ceschia, Marcello 
-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 3. April 2008 21:33
An: Heikki Linnakangas
Cc: Alvaro Herrera; pgsql-patches; Ceschia, Marcello; PostgreSQL Bugs
Betreff: Re: [PATCHES] Re: [BUGS] BUG #4070: Join more then ~15 tables let 
postgreSQL produces wrong data 


> What I propose we do is throw error for the moment, and make a TODO
> note to revisit the question after redesigning outer-join planning.
> Which is something I do intend to do for 8.4.


For me that's a good solution. 
My motivation for reporting this bug was to notice the developer about the 
problem.

Of course the query we did is a strange way to get a result, but it was 
possible without warning/error. At the moment we use a function to join the 
tables one by one and for the moment it is working.

Thank you for your helps

 Marcello

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

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

2008-04-04 Thread John Smith 
On Fri, Apr 4, 2008 at 7:46 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "John Smith" <[EMAIL PROTECTED]> 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/0001.004989E8.backup": No space left on device
>  > -- at this point there is a 0-byte file
>  > pg_xlog/0001.004989E8.backup present on disk
>  >  -- stop and start PG
>  >  -- recovery fails with: FATAL:  invalid data in file
>  > "0001.004989E8.backup"
>  >  -- NOTE: At this point removing 0001.004989E8.backup
>  > allows PG to start successfully
>
>  What do you see as the bug here?  Seems like reasonable behavior to me.
>
> regards, tom lane
>

I was expecting one of two things:
1. The zero-byte file is removed upon failure to write during
pg_stop_backup() (or )
2. The zero-byte file is ignored or deleted on startup, since the
administrator has no choice but to delete the file upon a failed
startup.

- John

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

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

2008-04-04 Thread Tom Lane 
"John Smith" <[EMAIL PROTECTED]> 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/0001.004989E8.backup": No space left on device
> -- at this point there is a 0-byte file
> pg_xlog/0001.004989E8.backup present on disk
>  -- stop and start PG
>  -- recovery fails with: FATAL:  invalid data in file
> "0001.004989E8.backup"
>  -- NOTE: At this point removing 0001.004989E8.backup
> allows PG to start successfully

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

regards, tom lane

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs