Re: [PATCH] Log details for client certificate failures
От | Masahiko Sawada |
---|---|
Тема | Re: [PATCH] Log details for client certificate failures |
Дата | |
Msg-id | CAD21AoDpBrbuSCsK=wgjJNg=A_L0Sx7pimZ24QL9SruxRZS=BA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Log details for client certificate failures (Jacob Champion <jchampion@timescale.com>) |
Ответы |
Re: [PATCH] Log details for client certificate failures
|
Список | pgsql-hackers |
On Wed, Sep 28, 2022 at 4:44 AM Jacob Champion <jchampion@timescale.com> wrote: > > On Tue, Sep 27, 2022 at 1:51 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > I think we can fix it by the attached patch but I'd like to discuss > > whether it's worth fixing it. > > Whoops. So every time it's changed, we leak a little postmaster memory? No. Since cluster_name is PGC_POSTMATER, we leak a little postmaster memory only once when starting up. application_name is PGC_USERSET but since we normally allocate memory in PortalMemoryContext we eventually can free it. Since check_cluster_name and check_application_name are similar, I changed both for consistency. Regards, -- Masahiko Sawada PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: