From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Jelte Fennema <postgres(at)jeltef(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, duspensky(at)ya(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16160: Minor memory leak in case of starting postgres server with SSL encryption |
Date: | 2021-03-21 14:32:21 |
Message-ID: | 20210321143221.GD20766@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Greetings,
* Andres Freund (andres(at)anarazel(dot)de) wrote:
> On 2021-03-16 14:44:55 -0400, Stephen Frost wrote:
> > OOMs errors should be gracefully handled and PG should continue to
> > function. Was that not the case..?
>
> Depends on what you mean with graceful. Unless you restart the database
> you'll eventually not be able to do anything anymore, since even the
> smallest memory allocation will fail?
Bit confused- I certainly agree with fixing the leak and back-patching
it, not sure how it came across otherwise. I was asking the questions
that I was to try to figure out if there was some other issue at play as
well.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2021-03-22 02:32:56 | BUG #16936: psql: \c service= not working |
Previous Message | PG Bug reporting form | 2021-03-21 09:17:20 | BUG #16935: Unable to provide map= option when combining clientcert=verify-full with some auth mechanisms |