Re: [GENERAL] More information

Try the vacuum command and see if that cleans up the database.
Then, if that fails, instead of dumping the entire db, use
the "pg_dump -t table dbname > dbname.table.out" to dump
each table that is still in good shape. Sorry I can't help
you with what the root cause is, but the above may get you
out of the jam.

Thomas

M Simms wrote:
>
> Okee - more information on my problem.
>
> Postgresql version 6.3.2 on redhat linux 5.2
>
> Here is a cut&paste from what happens
> ************************
> $ psql mydb
> Welcome to the POSTGRESQL interactive sql monitor:
>   Please read the file COPYRIGHT for copyright terms of POSTGRESQL
>
>    type \? for help on slash commands
>    type \q to quit
>    type \g or terminate with semicolon to execute query
>  You are currently connected to the database: mydb
>
> mydb=>\d
>
> Database    = mydb
>  +------------------+----------------------------------+----------+
>  |  Owner           |             Relation             |   Type   |
>  +------------------+----------------------------------+----------+
>  | myuid            | beep                             | table    |
>  | myuid            | history                          | table    |
>  | myuid            | history_seq                      | sequence |
>  | myuid            | historyb                         | table    |
>  | myuid            | other                            | table    |
>  | myuid            | record                           | table    |
>  | myuid            | recordb                          | table    |
>  +------------------+----------------------------------+----------+
> mydb=> select * from history_seq;
> sequence_name|last_value|increment_by|max_value|min_value|cache_value|is_cycled|is_called
> -------------+----------+------------+---------+---------+-----------+---------+---------
> (0 rows)
> mydb=> drop sequence history_seq;
> ERROR:  DeletePgTypeTuple: history_seq type nonexistent
> mydb=>
> ************************
>
> I have no idea what to do about this, cos I need to update my database
> but I cant do it with this happening, cos when I dump the database I
> get
>
> ************************
>
> $ pg_dump mydb > dump.out
> dumpSequence(history_seq): 0 (!= 1) tuples returned by SELECT
>
> ************************
>
> I need some solution to this if anyone knows. Surely a database this
> complex HAS to have some sanity-checking routines and database
> restoration. The documentation helpfully says that this section is
> missing, however. I have based a LARGE project on this, and so far, I
> cant start this project till this problem is fixed.
>
> Thanx
>
>                                 M Simms