Re: Introduce "log_connection_stages" setting.

From: Sergey Dudoladov <sergey(dot)dudoladov(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Jacob Champion <jchampion(at)timescale(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>
Subject: Re: Introduce "log_connection_stages" setting.
Date: 2023-01-30 18:58:19
Message-ID: CAA8Fd-owzkz4KJiV_Aku++aDzaZBvj1um1mBL5yekx864croRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, hackers

Thank you for the reviews. I've modified the patch to incorporate your
suggestions:
+ flag bits are now used to encode different connection stages
+ failing tests are now fixed. It was not a keyword issue but rather
"check_log_connection_messages" not allocating memory properly
in the special case log_connection_messages = 'all'
+ the GUC option is now only GUC_LIST_INPUT
+ typo fixes and line rewrapping in the docs

Regards,
Sergey

Attachment Content-Type Size
0002-Introduce-log_connection_messages.patch text/x-patch 22.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2023-01-30 19:04:10 Re: MacOS: xsltproc fails with "warning: failed to load external entity"
Previous Message Mark Dilger 2023-01-30 18:46:07 Re: Non-superuser subscription owners