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

Table corruption on drop

From: "Robert A(dot) Weiler" <rweiler(at)perfectsense(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Table corruption on drop
Date: 2000-12-22 20:26:52
Message-ID: 3A43B90C.3D33CE95@perfectsense.com (view raw or flat)
Thread:
Lists: pgsql-bugs
I'm using version 7.0.3 on Red Hat 7.0. I built the package using the
defaults. I have also experienced the problem on Red Hat 6.2 Here are
the deatils of the systems:

System 1:
Red Hat 6.2, Dell  Intel PIII/I810  700/133MHz, 128MB, 10GB IDE
Postgresql 7.0.3 built from .tgz using ./configure && make

System 2:
Red Hat 7.0 Homebuilt Dual PIII800/133 512MB,  1x20GB IDE, 1x30gb IDE
Postgresql 7.0.3 built from .tgz using ./configure && make

To reproduce the problem, write a simple sql file with 2 tables liek
this:

drop table1;
create table1 (
    v1 integer,
    v2 integer
);

create unique index  table1_index on table1(v1,v2);

drop table2;
create table2 (
    vi intteger,
    v2 varhcar(128),
    primary key (v2)
);

Run the script by redirecting from stdin to psql  - you should get a
delayed error like

ERROR: relation table1 does not exist.

Start psql and create the first table by hand, rerun the script.
Eventually you should get 'file not found' errors on the first table.

I've attached a sample .sql file and transcript.

If I create the tables before I drop them, everything seems to work
fine.

Bob Weiler
Perfect Sense Software

Attachment: postgresql.sql
Description: text/plain (605 bytes)
Attachment: psql.txt
Description: text/plain (3.0 KB)

Responses

pgsql-bugs by date

Next:From: Alexander KlimovDate: 2000-12-23 15:03:45
Subject: /bin/sh: !: not found
Previous:From: Tom LaneDate: 2000-12-22 18:12:14
Subject: Re: Backend crashes in 7.0.3

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