Re: Server closed the connection unexpectedly (memory leak) - Mailing list pgsql-bugs

From Andres Freund
Subject Re: Server closed the connection unexpectedly (memory leak)
Date
Msg-id 20230701025659.3o2hzm6prkrgfvzc@awork3.anarazel.de
Whole thread Raw
In response to Re: Server closed the connection unexpectedly (memory leak)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2023-06-24 12:56:06 -0400, Tom Lane wrote:
> Zu-Ming Jiang <zuming.jiang@inf.ethz.ch> writes:
> > My fuzzer finds a bug in Postgres, which makes the connection closed 
> > unexpectedly.
> 
> TBH, I think there's not much to be learned here, beyond "a
> ridiculously complicated query takes a ridiculous amount of memory
> to plan".  The reason for the backend crash is presumably that the
> OOM killer decided to zap it.  If you run the postmaster under a
> "ulimit -v" setting that's small enough to act before the OOM killer
> does, then you get an unexciting "out of memory" error.

One small thing I find is interesting is that it takes quite a while to
process cancel requests - which primarily appears to be because there's no CFI
anywhere in copyObject().

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Next
From: PG Bug reporting form
Date:
Subject: BUG #18010: Bug with installation/auto-configuration