Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up
Дата
Msg-id 20180628163642.lg2akxxkyplhxgni@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up  (Rui DeSousa <rui@crazybean.net>)
Ответы Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up  (Scott Ribe <scott_ribe@elevated-dev.com>)
Re: [External] standby replication server throws invalid memory allocrequest size , does not start up  (Rui DeSousa <rui@crazybean.net>)
Список pgsql-admin
On 2018-06-28 10:43:16 -0400, Rui DeSousa wrote:
> 
> 
> > On Jun 28, 2018, at 9:47 AM, Vijaykumar Jain <vjain@opentable.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


В списке pgsql-admin по дате отправления:

Предыдущее
От: Vijaykumar Jain
Дата:
Сообщение: Re: [External] Re: standby replication server throws invalid memoryalloc request size , does not start up
Следующее
От: Andres Freund
Дата:
Сообщение: Re: standby replication server throws invalid memory alloc requestsize , does not start up