public inbox for [email protected]  
help / color / mirror / Atom feed
From: Alfonso Escribano <[email protected]>
To: [email protected]
Subject: Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters
Date: Wed, 3 Dec 2025 17:38:28 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello,<br>
    I have test it with postgresql 17.7<br>
    I have been searching on postgresql src for commits related with
    client_connection_check_interval, and I only see initial commits in
    postgresql 14, I think it happends in all versions from 14 until 18,
    but I can only confirm on 17.7<br>
    <br>
    Regards,<br>
    Alfonso Escribano<br>
    <br>
    <div class="moz-cite-prefix">Adrian Klaver wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">On
      12/3/25 00:24, Alfonso Escribano wrote:
      <br>
      <blockquote type="cite">Hello,
        <br>
        I have seen an interaction between
        "client_connection_check_interval" and "log_lock_waits"
        parameters that it isn't documented (or I can't find it
        anywhere).
        <br>
      </blockquote>
      <br>
      What version of Postgres?
      <br>
      <br>
      <blockquote type="cite">Regards,
        <br>
        Alfonso Escribano
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <div dir="ltr">
        <div><br clear="all">
        </div>
        <div dir"ltr"="" class="gmail_signature"
          data-smartmail="gmail_signature">
          <div dir="ltr"> <br>
            <b style="color:rgb(105,105,105)">Alfonso Escribano</b> <br>
            <font color="#3333ff"> <a
                href="mailto:[email protected]"
                target="_blank">[email protected]</a> <br>
              <br>
            </font> <a href="https://www.meteologica.com";
              target="_blank"><img
                src="http://www.meteologica.com/assets/images/logo.png";
                width="200" height="16"></a> <br>
            <a>c/ Costa Brava 10 - 28034 Madrid</a> <br>
            <b style="color:rgb(105,105,105)">Office: </b> <a>+34 91
              456 10 01</a> <br>
            <br>
            <div> <font size="1"> <font color="#000000" face="arial,
                  sans-serif"> This email and any files transmitted with
                  it are confidential and may be privileged and are
                  intended solely for the use of the individual or
                  entity to whom they are addressed. If you are not an
                  addressee, any unauthorized direct or indirect
                  dissemination, distribution, publication, reading, or
                  copying of this message and any attachments is
                  strictly prohibited. If you have received this email
                  in error please notify the sender immediately, and
                  delete this email from your system. Email
                  communication does not guarantee the confidentiality,
                  integrity, or proper receipt of the messages sent.
                  Meteológica, S.A. accepts no liability for such
                  circumstances. </font> <br>
              </font> </div>
          </div>
        </div>
      </div>
    </div>
  </body>
</html>






view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox