Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t5rj2-00969l-LA for pgsql-general@arkaria.postgresql.org; Tue, 29 Oct 2024 19:17:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t5riz-002EXT-Vq for pgsql-general@arkaria.postgresql.org; Tue, 29 Oct 2024 19:17:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t5riz-002EXL-KZ for pgsql-general@lists.postgresql.org; Tue, 29 Oct 2024 19:17:53 +0000 Received: from mail-ej1-x641.google.com ([2a00:1450:4864:20::641]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t5rix-003V0s-6D for pgsql-general@lists.postgresql.org; Tue, 29 Oct 2024 19:17:52 +0000 Received: by mail-ej1-x641.google.com with SMTP id a640c23a62f3a-a9a977d6cc7so413122566b.3 for ; Tue, 29 Oct 2024 12:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730229469; x=1730834269; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YNi7qRETRDg3VlEq8bzit0XWIQUy2tLzO4Cfl5DoRcE=; b=kn1/yBfUP7b+VJxR2msD6MoxaL9R2z37Utur1VUtY3SQ6gj76gjUsGm888KVEqCvbk EABndAUl2YhX9g6/x11m7YO3NVLRrWpr09bMOEfvgR4cUdIskj4mgF6sq4to0lv9AJZ2 uo2RDuyVgowbChx9rQJIigOT/5+UzPD1q1zTOiOWmKxLb3VIcuIfHhWQZb0Sfe2wX+5j cGoDuk/ut20NTQsfFVHMwwziAizjNtrNmh8FW+MWvS7t5EnMyH/YCquqnL69rut1U+X9 TjPRywg+QHu//4OowJSxjjd6URi/wjR20LAyDQwcmd48YCPgLaI3vkGBJRV21u/9yClY Q03w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730229469; x=1730834269; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YNi7qRETRDg3VlEq8bzit0XWIQUy2tLzO4Cfl5DoRcE=; b=ALN1zMHiMmnQTIy5HihJxko0ahDXENssaTqm/3QmlZY26tsRpE5CTHRJ0KbJ1fyFcN vrN0p01dbqxB9vMADdshSdprMvzA7P0gJuAYdU+XWKk/7uDfAYX/HI7LWkNFp5rTqaeU E8hc2cwaLxvmN5E8YN9jGDIURpWChPEaoEeg3OF4B099nGJbQXxVcHeuWTvbalgCSwTg nLm2gWu1t3DtubJqhXwakpTcuGzghc22WSGy69G0LhpcFuHtp+3xl1ItgI2ScpbdDCPE eJqM1lHwUylJ0bxiSj2KM3gccH0LiK4v1SCOReBsNs1QII7WmDxXBA96E/nqR3oq/oqf j+bA== X-Gm-Message-State: AOJu0YzDeIBsk3qU5G3HWXWfXS2tnypqUZW5V9/yUlpbGac0CXBEynQ8 Y/ftWFV6WUM5L2rqYM4b6xWs15/5Q7ba6Cipp23QYbFUesBnf7WCMUf9hUOrcYPsRggagJgxxkC eeLc+LL3siVDMpJhMUSeaK5QvZpo= X-Google-Smtp-Source: AGHT+IFFxhf4r6dsl9GXHy9YAWaVd3XBis/8sX54u0MKlenmto3mhj/o17ztZt6fcsJYKL2Z7OfEe+9anaImUcsqPVM= X-Received: by 2002:a05:6402:51cc:b0:5c9:a5a9:1167 with SMTP id 4fb4d7f45d1cf-5cbbf8a4198mr12178330a12.10.1730229468559; Tue, 29 Oct 2024 12:17:48 -0700 (PDT) MIME-Version: 1.0 References: <8ec9d0b8dac0e38075c9630f02ef25b088f290ec.camel@lists.simkin.ca> <6e109baeabafa57970d7e8a9cdcb86abde8b14df.camel@lists.simkin.ca> In-Reply-To: <6e109baeabafa57970d7e8a9cdcb86abde8b14df.camel@lists.simkin.ca> From: Vijaykumar Jain Date: Wed, 30 Oct 2024 00:47:37 +0530 Message-ID: Subject: Re: Delays between "connection received" and "connection authenticated" because of localhost entries in hba To: Alan Hodgson Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000da81bc0625a27048" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000da81bc0625a27048 Content-Type: text/plain; charset="UTF-8" On Wed, 30 Oct 2024 at 00:40, Alan Hodgson wrote: > Well, I'm just throwing out something to check, but I meant on the server, > not the client. It's trying to resolve "localhost" to check the auth. If > there's a delay, that's probably where it is. > > I guess I just assumed that's where you were testing dig. > Yep. my mistake. i did not read it correctly. in order to discard the rule, it first has to find out by expanding the hosts in the rule, so yep, dns resolution might be the problem. also, the 4-5s delay is eerie similar to issues in the past. https://unix.stackexchange.com/questions/290987/resolving-hostname-takes-5-seconds maybe disabling ipv6 completely resolves this for the time being. -- Thanks, Vijay Open to work Resume - Vijaykumar Jain --000000000000da81bc0625a27048 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, 30 Oct 2024 at 0= 0:40, Alan Hodgson <ahodgson= @lists.simkin.ca> wrote:
Well, I= 9;m just throwing out something to check, but I meant on the server, not th= e client. It's trying to resolve "localhost" to check the aut= h. If there's a delay, that's probably where it is.

<= /div>
I guess I just assumed that's where you were testing dig.

Yep. my mistake.= i did not read it correctly. in order to discard the rule, it first has to= find out by expanding the hosts in the rule, so yep, dns resolution might = be the problem.

also, the 4-5s delay is eerie=C2= =A0similar to issues in the past.

maybe disabling ipv6 completely resolves this=C2= =A0 for the time being.


=
--
Thanks,
Vijay

Open to work
Resume -=C2=A0Vijaykumar Jain
--000000000000da81bc0625a27048--