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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
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:28:19
Message-ID: 20181022182819.uohpm24exao72zp3@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2018-10-22 20:18:32 +0200, Juan José Santamaría Flecha wrote:
> 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.

Yea, I think looking at that would be worthwhile. That an FD leak or
such could cause replay to get stuck is not that suprrising, but it
shouldn't cause corruption. That hints that something further is borked.

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-10-22 19:05:51 BUG #15451: Error adding foriegn key constraint
Previous Message Juan José Santamaría Flecha 2018-10-22 18:18:32 Re: BUG #15438: Standby corruption after "Too many open files in system" error