From: | Braeus Sabaco <braeus_sabaco(at)romanlegion(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | pg_dump fails sanity check |
Date: | 2001-01-26 19:01:07 |
Message-ID: | 3A71C973.72CBB54@romanlegion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Using version 7.0.2 (system is production, so I can't take it down for
minor releases) I enter:
$ pg_dump romanlegion > rdb.backup
and I get:
failed sanity check, table usergames was not found
Ok, fair enough, so:
$ psql romanlegion
romanlegion=# \d usergames
Table "usergames"
Attribute | Type | Modifier
------------+---------+----------
gameuserid | integer | not null
gameplayed | integer | not null
Index: unique_played
romanlegion=# select * from usergames ;
gameuserid | gameplayed
------------+------------
10 | 1
<snip>
442 | 10
(477 rows)
romanlegion=#
Now, it can find the table, describe the table, select from the table,
and the more complex queries I do on the site work just fine also. I
can make sure it is where I expect it to be.
$ su postgres
Password:
$ ls /var/lib/pgsql/data/base/romanlegion/usergames -al
-rw------- 1 postgres postgres 40960 Jan 25 23:43
/var/lib/pgsql/data/base/romanlegion/usergames
So now I'm out of ideas. Is there some known bug? Or is this just
being weird?
From | Date | Subject | |
---|---|---|---|
Next Message | adb | 2001-01-26 19:15:31 | Poor man's replication using WAL |
Previous Message | Doug McNaught | 2001-01-26 19:00:15 | Re: Performance: Unix sockets vs. TCP/IP sockets |