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 1t5rEI-0092px-De for pgsql-general@arkaria.postgresql.org; Tue, 29 Oct 2024 18:46:10 +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 1t5rEF-001zSa-IB for pgsql-general@arkaria.postgresql.org; Tue, 29 Oct 2024 18:46:07 +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 1t5rEF-001zSQ-3h for pgsql-general@lists.postgresql.org; Tue, 29 Oct 2024 18:46:07 +0000 Received: from mail-lj1-x244.google.com ([2a00:1450:4864:20::244]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t5rE9-003Upf-N5 for pgsql-general@lists.postgresql.org; Tue, 29 Oct 2024 18:46:06 +0000 Received: by mail-lj1-x244.google.com with SMTP id 38308e7fff4ca-2fb584a8f81so53627921fa.3 for ; Tue, 29 Oct 2024 11:46:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1730227560; x=1730832360; 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=4i7D+sanRO2NHxye4Gu2Z8RjwhI+hTIEjfAdugH5+ok=; b=OoAXRF/klcmjrOoDAtsl0gyz/gXAaGp4jtsNdI4kgndgw/DW2D9dQZeLbd3ADvLco5 WGiD9MbF2ET9oZugfIvvASi38YTOE8xdL2Fx3YwUhkGh8S7cpiyzc5296beU0woTbZfc ntQQjvJ1AMLpi9CTL9iRj1dSGub+rOLhX3BuZTkd/xExYS3B7l+qGNSbvpY+doCHl81B INDMW9lVl8LV5mkZmTwB0FK+yirNdPUss7n9UGUtiTKuVm90PkruPHeydbD0KjHGjPS4 sjC++Ar8TU8rOmbwjWhG1UOGBOtfhnoBn8/UNNXv/YPctB8J4C4WO4iu2/5nXIjMxhCH SqmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730227560; x=1730832360; 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=4i7D+sanRO2NHxye4Gu2Z8RjwhI+hTIEjfAdugH5+ok=; b=lcyr0KOidHb6zBpJybgibcVqv2ilE82vkSxf/qet6kiVO+vXep/RX7oTkfsrGs9+uG jAdBYvPEU04+PpQtJfcn/CgIhkmqrhb8/rWNL4hZSUsR2L17ULjdfaTN7hdne8mAJ1Fe HrDLu+OmqrcvnS6e9W7gLX+mZHwkZr6UFRGl8IqaA74n6oSl+O41WpRN5lzVjUH0634J eexT0vSXl6/RVNFgpnv7cY9CWsoYYz30uY0aLaNQpkS5L1S0apfkI7MWoJSVDshX6eNz 36deEIBvUkUhyuEFk4O2SKWntZJvtpJmYAPW9aHeINPMgoPCoaAse/i8S8M7VI2fkfaN ehww== X-Gm-Message-State: AOJu0Yx4C9Juzh9EMr/Y+nTtvUtvXwkU6sj+DwSmmbxC/WnQikRf/Zbd 3kZSR//b4R/W6ejWDNV/1rKC5Zq0yUL0qD0j8d9ix3GXxBANXuq1OKvMEUVyLK+TxdQvno0um9+ 0mZjcwJZXXO8PerqbCgiwa/F4z4hbCSW9 X-Google-Smtp-Source: AGHT+IHc4kW33JyK59M5kyDmDeIC6iCe7ktyMqT7PNo/EKF/Q1X5dyQ374wYiM+VelikImZLlGaTUED7mDqXKrcK+/0= X-Received: by 2002:a05:651c:506:b0:2fb:4603:da13 with SMTP id 38308e7fff4ca-2fcbe0989bfmr51242061fa.39.1730227559750; Tue, 29 Oct 2024 11:45:59 -0700 (PDT) MIME-Version: 1.0 References: <8ec9d0b8dac0e38075c9630f02ef25b088f290ec.camel@lists.simkin.ca> In-Reply-To: <8ec9d0b8dac0e38075c9630f02ef25b088f290ec.camel@lists.simkin.ca> From: Vijaykumar Jain Date: Wed, 30 Oct 2024 00:15:47 +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="000000000000146bfb0625a1ff1d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000146bfb0625a1ff1d Content-Type: text/plain; charset="UTF-8" On Wed, 30 Oct 2024 at 00:04, Alan Hodgson wrote: > On Tue, 2024-10-29 at 16:30 +0000, Daniel Westermann (DWE) wrote: > > Delays between "connection received" and "connection authenticated" > because of localhost entries in hba > > > Maybe check that "files" is the first mechanism for hosts lookups in > nsswitch.conf. > > afaik dig doesn't follow the same name resolution path as glibc. > a connection received should mean resolution was done, right ? am i missing something? I could try adding delay with traffic control, but then if a connection established is logged in the log, then name resolution is ok ? or the syscall to md5 is slow , does it work faster for trust ? just saying :) -- Thanks, Vijay Open to work Resume - Vijaykumar Jain --000000000000146bfb0625a1ff1d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, 30 Oct 2024 at 00:04, Alan Ho= dgson <ahodgson@lists.simkin= .ca> wrote:
On Tue, 2024-10-29 at 16= :30 +0000, Daniel Westermann (DWE) wrote:
Delays between "connection received" and "= ;connection authenticated" because of localhost entries in hba

Maybe check that "files" is th= e first mechanism for hosts lookups in nsswitch.conf.

<= div>afaik dig doesn't follow the same name resolution path as glibc.


a connection re= ceived=C2=A0should mean resolution was done, right ? am i=C2=A0missing some= thing?
I could try adding delay with traffic control, but then if= a connection=C2=A0 established is logged in the log, then name resolution = is ok ?

or the syscall to md5 is slow , does it wo= rk faster for trust ? just saying :)=C2=A0

--
Thanks,
Vijay

Open = to work
Resume -=C2=A0Vijaykumar Jain
--000000000000146bfb0625a1ff1d--