User Tools

Site Tools


how_to:repairing_corrupted_database

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
how_to:repairing_corrupted_database [2016/04/06 12:15] paulhow_to:repairing_corrupted_database [2016/04/06 12:16] – [Finding the problem table/index] paul
Line 32: Line 32:
 Then type (or copy/paste) 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 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===== =====unexpected chunk number=====
how_to/repairing_corrupted_database.txt · Last modified: 2024/01/15 11:35 by paul