Re: Re: [ANNOUNCE] PostgreSQL 7.0 a success - Mailing list pgsql-general

From Denis Perchine
Subject Re: Re: [ANNOUNCE] PostgreSQL 7.0 a success
Date
Msg-id 00052510090603.18188@dyp
Whole thread Raw
In response to Re: Re: [ANNOUNCE] PostgreSQL 7.0 a success  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: Re: [ANNOUNCE] PostgreSQL 7.0 a success  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
> > Sometimes a table doesnt exist anymore but it's still listed in
> > pg_class table, or the opposite, or you did a physical backup and you
> > wanna restore the db, and other things that could be improved and more
> > documented.
>
> example?  some way to recreate for debugging?

1. When you have created temp table and just killed frontend. Backend realize that connection
is broken and somehow did not remove the table from pg_class. Then it will exists on the disk
and in pg_class.
2. When you do operations with large objects (they are treated as relations also) and you do rollback
or again connect broken. Or you do lots of lo_unlink and rollback or just broke connection. Then it will
be in pg_class, but file will already be deleted. This can happend if you do big transaction with lo like:
select lo_unlink(lo) from lo_container; And you have more than 3000 large objects associated with
lo_container.lo.

--
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres Instability
Next
From: Lamar Owen
Date:
Subject: Re: Postgres Instability