| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Sam Nelson <samn(at)consistentstate(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Memory Errors |
| Date: | 2010-09-08 19:01:51 |
| Message-ID: | AANLkTike1AnNjxBx+OKOTTB915VuWFx5HhMKMKBa1NLK@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Sep 8, 2010 at 12:56 PM, Sam Nelson <samn(at)consistentstate(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tamanna madaan | 2010-09-08 19:11:54 | Re: error while autovacuuming |
| Previous Message | Darren Duncan | 2010-09-08 18:57:28 | Re: how do i count() similar items |