Out of memory in CIFS leads to database crash - Mailing list pgsql-bugs

From Umesh Kirdat
Subject Out of memory in CIFS leads to database crash
Date
Msg-id 1389089000.56167.YahooMailNeo@web193101.mail.sg3.yahoo.com
Whole thread Raw
Responses Re: Out of memory in CIFS leads to database crash
List pgsql-bugs
Hello All,=0A=A0=0AIn our setup under heavy load (too many client performin=
g=0Aupdates) we have observed the underlying CIFS module runs out of memory=
 and the=0Adatabase crashes or goes in recovery mode.=0A=A0=0ANov 28 09:17:=
32 ng78 kernel: CIFS VFS=0A(1006f1e5e,pid=3D19342): Error in Open =3D Out o=
f memory<3> ISVS(0615,i=3D96)=0Aro nOe u fmoy<3> CIFS VFS(1006f16,pid196) r=
or i pn u fmmor=0ANov 28 09:17:32 ng78 postgres[19342]: [10-1] 192.168.20.7=
8 19342 2013-11-28=0A09:17:32.882 PST ERROR: could not open file "base/1638=
4/16794":=0ACannot allocate memory=0ANov 28 09:17:32 ng78 postgres[19342]: =
[10-2] 192.168.20.78 19342 2013-11-28=0A09:17:32.882 PST STATEMENT: select =
=0A=A0=0AThe physical memory on the machine is 64 GB=0APostgres version 9.0=
.4=0AHardware is 64 bit=0A=A0=0AI wish to know why is the database crashing=
 if the file=0Aopen fails? Why can't it handle it gracefully by rolling bac=
k the transaction?=0AUmesh

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Next
From: sahareanish@gmail.com
Date:
Subject: BUG #8746: While Calling Trigger on same table