#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Apr 2013
    Posts
    3
    Rep Power
    0

    Vacuum and Reindex Problem


    I have a problem to run vacuum and reindex my db.

    Everytime I run vacuum, it will stuck at a table.
    ERROR: could not read block 76 of relation 1663/16385/545891: success

    I will reindex the table and when I run vacuum again, it will stcu at another table

    This problem will continue happen and I have no idea whats actually the error

    I try to reindex database but the error comes out:
    ERROR: could not read block 0 of relation 1663/16385/545909: Bad address

    Can someone help?
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Frequenter (2500 - 2999 posts)

    Join Date
    Oct 2003
    Location
    Germany
    Posts
    2,785
    Rep Power
    348
    Originally Posted by firdzak
    Everytime I run vacuum, it will stuck at a table.
    ERROR: could not read block 76 of relation 1663/16385/545891: success
    I'd say your harddisk has an rror. Shutdown Postgres now and make a physical copy of the data directory (and other important data)

    Then run some tool on the harddisk to detect and mark bad sectors.
    I will not read nor answer questions where the SQL code is messy and not formatted properly using [code] tags.
    http://forums.devshed.com/misc.php?do=bbcode#code

    Tips on how to ask better questions:
    http://tkyte.blogspot.de/2005/06/how-to-ask-questions.html
    http://wiki.postgresql.org/wiki/SlowQueryQuestions
    http://catb.org/esr/faqs/smart-questions.html
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Apr 2013
    Posts
    3
    Rep Power
    0
    Thanks shammat

    I will do the steps and update this thread if it is really hardware failure problem

    Regards
  6. #4
  7. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Apr 2013
    Posts
    3
    Rep Power
    0
    Sorry

    Forgot to update

    It is really a hard disk problem and when we move to another hard disk, the error gone.

    Thanks to shammat on this

    Regards

IMN logo majestic logo threadwatch logo seochat tools logo