Differences

This shows you the differences between two versions of the page.

--- how_to:repairing_corrupted_database [2016/04/06 12:15] – paul
+++ how_to:repairing_corrupted_database [2016/05/04 09:31] – [unexpected chunk number] paul
@@ Line 32: / Line 32: @@
 Then type (or copy/paste)
-  select n.nspname AS schema, c.relname AS tablename, c.reltype as type from pg_class c inner join pg_namespace n on (c.relnamespace=n.oid) where c.relfilenode=<filename>;
+  select n.nspname AS schema, c.relname AS tablename, c.relkind as kind from pg_class c inner join pg_namespace n on (c.relnamespace=n.oid) where c.relfilenode=<filename>;
 In the above example error message <filename> would be replaced by 512312
-If 'type' is 'i' then the damaged relation is an index, so a database reindex should fix the problem. If it is 'r' then it is a normal table, or if it is 't' then it is a 'toast' table (see below).
+If 'kind' is 'i' then the damaged relation is an index, so a database reindex should fix the problem. If it is 'r' then it is a normal table, or if it is 't' then it is a 'toast' table (see below).
 =====unexpected chunk number=====
@@ Line 50: / Line 50: @@
 Unfortunately, there is no easy way to find which record is damaged, so you need to scan the entire table.
-Go to a command prompt in the VPOP3 directory and run 'psql' (in version 5 only). The default password is 'vpop3pass'
+Go to a command prompt in the VPOP3\pgsql\bin directory and run 'psql -U postgres -p 5433 vpop3' (in version 3 or 4 omit the '-p 5433'). The default password is 'pgsqlpass'
 ====Finding the problem message====

PSCS Wiki

User Tools

Site Tools

Differences

Page Tools