Re: archive falling behind

From: German Becker <german(dot)becker(at)gmail(dot)com>
To: "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: archive falling behind
Date: 2013-05-09 15:27:26
Message-ID: CALyjCLs4F9CbaS=5MUbNXmWmzRD4kgdUxoP1CZu3srBcJu3O3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

David, You were absolutly right. I broght the server down and it was a
faulty RAM indeed.Thank you very much for your help!

On Sat, Apr 27, 2013 at 5:51 PM, David F. Skoll <dfs(at)roaringpenguin(dot)com>wrote:

>
> From: German Becker <german(dot)becker(at)gmail(dot)com>
> Subject: Re: archive falling behind
>
> > Actually this seems like a very strange filesystem /hw problem. The
> > wal segments keep "changing" even after I stoped the database and
> > noone is supposly accesing it:
>
> I've seen this before. It was bad RAM. I bet it's a hardware problem
> for you as well... either bad RAM or a flaky disk.
>
> In my case, I found it out because I got syntax errors in the
> PostgreSQL logs: SELGCT was not a valid keyword. It turns out
> that the flaky RAM was flipping bit 1 occasionally, so it would
> randomly add or subtract 2 from a byte.
>
> Regards,
>
> David.
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message German Becker 2013-05-09 15:45:55 Point in time recovery + replication
Previous Message Rodrigo Barboza 2013-05-08 23:24:46 Delete xlog files