Re: Server closed the connection unexpectedly (memory leak)

Hi,

On 2023-06-24 12:56:06 -0400, Tom Lane wrote:
> Zu-Ming Jiang <zuming(dot)jiang(at)inf(dot)ethz(dot)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