Loosing files after backend crash - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Loosing files after backend crash
Date
Msg-id 200104022145.f32LjSZ16279@hub.org
Whole thread Raw
Responses Re: Loosing files after backend crash
List pgsql-bugs
Konstantin Solodovnikov (ks@tcnet.ru) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Loosing files after backend crash

Long Description
After a backend crash the file for my sequence cannot be found.

I use PostgreSQL 7.1RC1 compiled by GCC 2.95.2 on FreeBSD 4.2-STABLE and that's what I encountered.

During execution of some sql code backend crashed (the reason for it's crashing is not the actual topic of this
report).
I successfully re-run psql without restarting the postmaster.
And tried to delete the sequence, which i created in the previous session.
That's what pgsql told me:
---8<---
Netflow_Test=# drop SEQUENCE seq_i___data_buffer ;
ERROR:  cannot open seq_i___data_buffer: No such file or directory
---8<---
I examined the system tables (ps_class) and found the tuple, describing my sequence.
The "relfilenode" attribute of the tuple contained the value "326210". I tried to find the file with that name in the
databasedirectory - it really was not there. 
Thus, the backend crash has led not only to impossibility to complete my task, but also to loosing some data. The
sequencewas actually created in an already committed transaction, not in the one, that crashed. 
Another problem is that I cannot fix the situation (drop that sequence) by standard PGSQL means.
I had to create an empty file with that name ("326210") for "DROP SEQUENCE" command to successfully complete.

As i guess, the situation is not reprodusable. Backend crashed many times before w/o such problems.

A little additional question/proposition: can there be any tool, which could find and resolve the errors in the system
tables?

Best Regards,
Konstantin Solodovnikov.

Sample Code


No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Table constraint ordering disrupted by pg_dump
Next
From: Tom Lane
Date:
Subject: Re: Loosing files after backend crash