Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j6f5Q-0007m6-On for pgsql-general@arkaria.postgresql.org; Tue, 25 Feb 2020 18:37:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j6f5P-0002Ed-80 for pgsql-general@arkaria.postgresql.org; Tue, 25 Feb 2020 18:37:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j6f5O-0002EW-UL for pgsql-general@lists.postgresql.org; Tue, 25 Feb 2020 18:37:38 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j6f5M-0007CG-P0 for pgsql-general@postgresql.org; Tue, 25 Feb 2020 18:37:38 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 36E6A220AA; Tue, 25 Feb 2020 13:37:35 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 25 Feb 2020 13:37:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=T Dx0zRXDU3HPcWTRCbif2jQpfPFjV4Dp2d+2PKJSlas=; b=Xe7cIMbu+GyL6UPzK TlOBfAy98KFzkbs0gIt2JIYdEvs36AJCETz5wWf3wBjOtKSNJ12yHyLie1FK0hmf tiG6tDerwmsLWMJ8t//hTMw3Wee4dDzVvVvBC9PjLWFtOUCqqTgeLb4VwIMd36lH D/d2GQb601PU1I90iDt3WsGcMRm5c+/LdLb8/TCUNq4CBv3L62tM8HOycIr7IjAQ GfZcn2AmVQDWukzvDb7c6MTTXLIb/qow5n3jRRDv6twFD9zwQWAsJK2ZBmSypb9m aAwJwk/WgAB1YdLzhpU11HsTiCsvDFMIbpCe4eQvmw5/zOTldH2bdW2xN4qdDeVX 5/0NQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=TDx0zRXDU3HPcWTRCbif2jQpfPFjV4Dp2d+2PKJSl as=; b=asVesjQ3Zww2/25qElqlRfpRVRfU+uMThuZwsOdceyD+mfcx3TMUcRdIg Oh4Ecl2ruYdfDZdXrLuEub+0DHUBwP+ZtYSSPuRcdMxP8JDfLaG7YtghhiC/zSTH dFP8gUCgBe48sbK1gVh43aVSpLxdzkabntPeeiVOQvHSbZClKZ3krXuaYHP4pooY 71OuMdvwP/GdHJlPNfRgu10OeF0VkXWfco3CtowCyRQS4GNDOLAYSWZiGUIkyr5D lDZ6rxXUp6hnzANBzkW5DpH0V5hn+LWd5eWl3GQH/NcDcJLeDsKET664Z3irCuyJ zTlni+YOuYbS+rk+5bI/GJU41xARQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrledvgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucfkphepjeegrdelgedrjeefrddvvddvnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvh gvrhdrtghomh X-ME-Proxy: Received: from ranger.suse (unknown [74.94.73.222]) by mail.messagingengine.com (Postfix) with ESMTPA id 90CED30610E9; Tue, 25 Feb 2020 13:37:34 -0500 (EST) Subject: Re: LDAP with TLS is taking more time in Postgresql 11.5 To: Mani Sankar Cc: pgsql-general References: <319e70c3-cd99-8bf9-260d-49064ba402c5@aklaver.com> <1e9458a5-6f83-7715-3b48-a1bfae35ca72@aklaver.com> From: Adrian Klaver Message-ID: <27f81267-cdee-c6c6-5ab3-9a1042fe5212@aklaver.com> Date: Tue, 25 Feb 2020 10:37:33 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/25/20 10:23 AM, Mani Sankar wrote: > Hi Adrian, > > Both the machines are in same network and both are pointing towards the > same LDAP server I don't see any errors in the Postgres logs. You probably should take a look at the LDAP server logs to see if there is anything there. You could also turn up the logging detail in Postgres to see if it reveals anything. > > Regards, > Mani. > -- Adrian Klaver adrian.klaver@aklaver.com