From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Rui DeSousa <rui(at)crazybean(dot)net> |
Cc: | Vijaykumar Jain <vjain(at)opentable(dot)com>, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [External] Re: standby replication server throws invalid memory alloc request size , does not start up |
Date: | 2018-06-28 16:36:42 |
Message-ID: | 20180628163642.lg2akxxkyplhxgni@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 2018-06-28 10:43:16 -0400, Rui DeSousa wrote:
>
>
> > On Jun 28, 2018, at 9:47 AM, Vijaykumar Jain <vjain(at)opentable(dot)com> wrote:
> >
> > Thanks Scott.
> >
> > fsync is on.
> >
> > postgres=# show fsync;
> > fsync
> > -------
> > on
> > (1 row)
> >
>
> Yeah, I agree with Scott; it sounds like fsync() is being shorted
> somewhere in the I/O path. Are you using a RAID controller; if so is
> the cache setting — write through or write back? If it’s write back
> then writes are being cached and a power outage will lead to data
> corruption — the only saving grace at that point would be the battery
> backup logic on the controller which may or nay not be trustworthy.
How are you making the inference that that's the problem? It could very
well be a postgres bug or somebody having used pg_resetxlog or.. ?
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-06-28 16:39:42 | Re: standby replication server throws invalid memory alloc request size , does not start up |
Previous Message | Vijaykumar Jain | 2018-06-28 15:18:08 | Re: [External] Re: standby replication server throws invalid memory alloc request size , does not start up |