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 1s68Cl-00AG9p-0F for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 12:21:27 +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 1s68Cj-00AsgI-1z for pgsql-hackers@arkaria.postgresql.org; Sun, 12 May 2024 12:21:25 +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 1s68Ci-00Asg8-OR for pgsql-hackers@lists.postgresql.org; Sun, 12 May 2024 12:21:25 +0000 Received: from fout3-smtp.messagingengine.com ([103.168.172.146]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s68Cc-000dB9-DR for pgsql-hackers@postgresql.org; Sun, 12 May 2024 12:21:23 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id AF24F1381142; Sun, 12 May 2024 08:21:16 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 12 May 2024 08:21:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1715516476; x=1715602876; bh=HferlQWSS2lyG2at03l7W7/M2oqT0NBV1EIEThkeQbg=; b= MxmAku++7SDgquiv+Vg3lx8jId/zjVY7QmgXuC1Rk77RC5VulzIVcZSab3hPEo97 0q5OWfWocU9SvBIwoYbe1ckS/XyE3Gf6z2OtXHLxzKTKhmvfbuvmTUG68LpcbyS6 qNZM2ml/9mdQeB63UwdWjLAyQzOe1b37UQsZmdXDhEKNJ0jxeN1KN6LpvkrVdfGB WbLiaJL+z9d1puGCEYBKqg0E8GG0+0s3tGzXXqjaeFVCpKP1PStxAmujkCZzCpjQ Z32FpQHtRWZCpFwwkE3rwSeB4PZqjFzJCV/hV48QjRVmllC+3MPY32w7wXPCt+37 BpLW+czPl/kpUpHQP/Uxrw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1715516476; x= 1715602876; bh=HferlQWSS2lyG2at03l7W7/M2oqT0NBV1EIEThkeQbg=; b=H UJRBNY6j568mDjljeUM5SEaqnngKPfAhzUAIa7zjUlNCEPqjfHT/wdY3/BlzwAkx cu0f429WBWvzeIKtFnry8gpZh1MmoqpM9bIdQ9Hs9xmh5cbygDF7VdM8slwOXhH4 jDuPhPjsR4HehAuppcOWJYMJpLkOLYho1GdRX4ENR9Mg5df+XdUDPXS7pzToBwkF c0GfHL0A+5qdTf0oPakyAKsyHaZq8JVY51jffKlb3bV9fg/1rOzz4LXwhknGiB46 H6lXbKBgYVdodgrm9h7V2yzoorKykF64L2UxpNsNrcJLqg0wUpK+XsofvwoGqVs3 nDg2f9C5yYA4ONyPQmsgg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegvddgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr segvihhsvghnthhrrghuthdrohhrgheqnecuggftrfgrthhtvghrnhepudfgjefffeelfe dvgedvjedvieehvefghfejgfduhfevvdejveefheetlefgveefnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhesvghishgvnhhtrh gruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 12 May 2024 08:21:15 -0400 (EDT) Message-ID: <4852776b-ed8b-4a39-80ee-86223fe6d389@eisentraut.org> Date: Sun, 12 May 2024 14:21:15 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Logging which interface was connected to in log_line_prefix To: Greg Sabino Mullane , pgsql-hackers References: Content-Language: en-US From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 06.03.24 16:59, Greg Sabino Mullane wrote: > Someone on -general was asking about this, as they are listeningĀ on > multiple IPs and would like to know which exact one clients were > hitting. I took a quick look and we already have that information, so I > grabbed some stuff fromĀ inet_server_addr and added it as part of a "%L" > (for 'local interface'). Quick patch / POC attached. I was confused by this patch title. This feature does not log the interface (like "eth0" or "lo"), but the local address. Please adjust the terminology. I noticed that for Unix-domain socket connections, %r and %h write "[local]". I think that should be done for this new placeholder as well.