On Wed, Sep 8, 2010 at 12:56 PM, Sam Nelson <s...@consistentstate.com> wrote: > Hey, a client of ours has been having some data corruption in their > database. We got the data corruption fixed and we believe we've discovered > the cause (they had a script killing any waiting queries if the locks on > their database hit 1000), but they're still getting errors from one table:
Not sure that's really the underlying problem. Depending on how they killed the processes there's a slight chance for corruption, but more likely they've got bad hardware. Can they take their machine down for testing? memtest86+ is a good tool to get an idea if you've got a good cpu mobo ram combo or not. The last bit you included definitely looks like something's corrupted in the database. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
