Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you want your data back in a hurry and it's worth something to you, then the professional support option should be simple enough.</p> <p>Some things to check, now that you've got a full backup of all your database (that's base, pg_clog, pg_xlog and all the other folders at that level).</p> <ol> <li><p>Does that file actually exist? It might be a permissions problem rather than the file actualy going missing.</p></li> <li><p>Check your anti-virus/security packages - have they mistakenly quarantined the file? If you can exclude PostgreSQL's database directories from scans/active scans that's worthwhile too.</p></li> <li><p>Make a note of everything you can remember about when this happened and what happened just before. This will help with troubleshooting for you or a consultant.</p></li> <li><p>Check the logs likewise - this error will be logged, find the first occurrence and see if there's anything odd before.</p></li> <li><p>Double-check you really do have all your existing files backed up, and restart PostgreSQL.</p></li> <li><p>Try connecting as user postgres to database postgres or database template1. If that works then the file is one of your database files rather than the global list of users or some such.</p></li> <li><p>Try creating an empty file with the right name (and permissions - check the other files). If you are really lucky it's just an index. Otherwise it could be a data table you can live without. Then you can dump other tables individually.</p></li> <li><p>OK - if you're here then you can connect to your DB. Those numbers in the file-path are PostgreSQL's OIDs identifying system objects. You can try a couple of useful queries here. These two queries should give you the IDs of the databases and then the object with the missing file. This is useful information for your professional too.</p> <p>SELECT oid, datname, dattablespace FROM pg_database; SELECT * FROM pg_class WHERE relfilenode = 16691;</p></li> </ol> <p>Remember <em>make sure you have the filesystem backup before tinkering</em>.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to Recover PostgreSQL 8.0 Database
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRichard Huxton
    1. USRichard Huxton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, Richard! Just some remarks: I don't know what happened, it could be a power failure. I can connect to both databases (template1 and the one that is corrupt). Nothing weird in the logs, what bugs me most is that none of the files/directories (1663/17269/16691) exists. I will contact professional support.
      singulars
      1. PO
      1. USRicardo Peres
    2. COThey'll probably cry once they hear you are on 8.0 - that was released in 2005! I'm surprised the directories don't exist - particularly 1663 - that should be your database. I've edited the answer with some more trouble-shooting you can do.
      singulars
      1. PO
      1. USRichard Huxton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload