Re: BUG #15438: Standby corruption after "Too many open files in system" error

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: andres(at)anarazel(dot)de
Cc: alvherre(at)2ndquadrant(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15438: Standby corruption after "Too many open files in system" error
Date: 2018-10-22 18:18:32
Message-ID: CAC+AXB25UB4HuZpyw5p5tn0-NCD7BkV0iHx=Ujx+soFPjJcoDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

When you say corruption, do you mean that the data was corrupted
> afterwards? Or just that the standby spewed errors until you restarted
> with adjusted limits?
>

We didn't do a proper low level check to verify that the database was
corrupted, but the symtopms took us to belive so: after a restart the
system crashed almost immediately with and 'invalid memory alloc request
size', no matter the user limits.

There is a backup still available if any test can be of interest.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-10-22 18:28:19 Re: BUG #15438: Standby corruption after "Too many open files in system" error
Previous Message PG Bug reporting form 2018-10-22 17:57:42 BUG #15450: postgis 2.4 and postgis 2.5 extention not properly built