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 1tEWKI-007tBd-0x for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:16: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 1tEWKG-00A4mV-Ls for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:16:08 +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 1tEWKG-00A4mM-Aq for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:16:08 +0000 Received: from mail-oa1-x29.google.com ([2001:4860:4864:20::29]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEWKC-003F1W-E0 for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:16:07 +0000 Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-2958ddf99a7so2142330fac.2 for ; Fri, 22 Nov 2024 08:16:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732292163; x=1732896963; 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=wzaL7V1EkCw5n+URk2U3cm2k4gLontd6EQg3bshj3ZY=; b=a5CpZzXoL6jv/gk81NvtjGMfZ5t4th+BUqHipsI+mXqtcFbbKurKVCp6Drrx8ZjGAI S9k7YiAXtFDtTcB215PQCkSLJsFcyqEVWE2tKT4GgTwSQQ2ESkkQ0EVN/uBYmLz1SYEm QrDajVeZGdIvrd0Jvwrshfd+Y0wb8k0tNq1fhNrw9jbbHjL50rGZ6tDal9PLOXkdvMmM I1WUJpA+c90rS+B8Qw4+7ke2b8jbS9gAtgnjCqTF1JSEvVULHXnoAN0LDWfFWAk1Fqum T0RDokO4BLl3s8Zct2vNXCsp/U5sc/YuZKn1gj0vw6mIWCTFDLJcpZVzt8dFzfwPjKjv lp3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732292163; x=1732896963; 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=wzaL7V1EkCw5n+URk2U3cm2k4gLontd6EQg3bshj3ZY=; b=BpfqBQtTjYMZ0vgk+s2BncmguaOB550LFdMlGegqz1pjSyvE72UK3xoViVwTYvPwlp As9rs7pZgOTuLC7UtVXPb+bbm+xyhJo7Y1f6X8ccj5r+n1lmeR8rbstmPRC3C79K9PLl nAg67l6fl+a2fEk4du51zqrTwkFROCskWW1vX3Z5fXdsQEyQVMu/GbcZVxbsqW/JahLg YPOajhigKt5KyuAZm3HvKk63h01+4FAf1iNJanowbhgI9oJHgbQZdNNU87/bbhM8B42j d0qblIQderiS1TrKkUdHKRK2KAUhJo1yh0+4dHU7812tlwgosmg1JqN1qpGX8O3inztO cfxg== X-Gm-Message-State: AOJu0YyIp/k+Z/pAgxzIL8lJXsotsYtCTDA3jnhP9wZIlw3tgKmmRr4k xTHJcxzBhhvE/7EtvvAXFw+9kq2JNn6E7j4P6GzJ4CUbgzpNPT06bZuOOHAJ2teMvK1WKfbmrwF oyM5G4J/oPEtr3JlopZF8XzDsRL8= X-Gm-Gg: ASbGncudp2HIr4iCLFDSyeYJLK+lacyF0vTrIf9KV7y2rij56dp5zA4fb/rt8vDJfvh F3DvkV1BYlCwFpQ9nOofANE7mmmlwu78= X-Google-Smtp-Source: AGHT+IEp8KJovb2inKJ+tmyeBJ+13FMsf8BYkQ+jmwY2KbcnTEAOxHR9L+CFCVNUH/cKGvWus/4B806oKBfG/rJB2GY= X-Received: by 2002:a05:6871:3a0d:b0:296:56d5:26c with SMTP id 586e51a60fabf-29720c41d0dmr3377025fac.24.1732292163164; Fri, 22 Nov 2024 08:16:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Fri, 22 Nov 2024 09:15:22 -0700 Message-ID: Subject: Re: PostgreSQL Log Info To: Jethish Jethish Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000086090062782b38e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000086090062782b38e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 22, 2024 at 12:32=E2=80=AFAM Jethish Jethish wrote: > If an select query is fired I need the query returned values needs to be > logged in my PostgreSQL log file. > Then the answer is no, and unlikely to become a feature anyone would develop or that we'd accept. A more innovative solution is going to need to be thought up to satisfy the security people that want to know what data was acquired from their system by either their users or semi-privileged hackers (privileged exploits would likely just disable such logging anyway). The space of setting up a proxy server in between clients and the PostgreSQL server is under-explored as a means by which to incorporate such functionality externally to the core server. David J. --000000000000086090062782b38e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Nov 22, 2024 at 12:32=E2=80=AFAM Jethish Jethish &= lt;jethish777@gmail.com> wro= te:

If an select query= is fired I need the query returned values needs to be logged in my Postgre= SQL log file.

Then the answer is no, and unlikely = to become a feature anyone would develop or that we'd accept.
<= br>
A more innovative solution is going to need to be thought up to= satisfy=C2=A0the=C2=A0security people that want to know what data was acqu= ired=C2=A0from their system by either their users or semi-privileged hacker= s (privileged exploits would likely just disable such logging anyway).=C2= =A0 The space of setting up a proxy server in between clients and the Postg= reSQL server is under-explored as a means by which to incorporate such func= tionality externally to the core server.

David J.
--000000000000086090062782b38e--