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 1tEWUZ-007un0-Ey for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:26:47 +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 1tEWUY-00AAwV-0g for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:26:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tEWUX-00AAwM-Kd for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:26:45 +0000 Received: from mail-qv1-xf35.google.com ([2607:f8b0:4864:20::f35]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEWUV-003JCi-Gw for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:26:45 +0000 Received: by mail-qv1-xf35.google.com with SMTP id 6a1803df08f44-6d41dbf6cfbso15742136d6.3 for ; Fri, 22 Nov 2024 08:26:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732292801; x=1732897601; 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=tI/ul8ZfuzCLRKtKvNgdJwGLAJk7gXb7MrCiDeVXmB4=; b=JBa699AQtCMN4LCROIGpOO4WGLalkR9pt8zutvBmQeXSdb+mTCz8Cb3uQYkDhLE7b2 GCVos0KtN73FSNQxV0XpPZzkUd/9DNcezqmlF5W8Bk2Z0o+DmxU/BmxhVzOF5Gbtcs4Z K7q5SNqwPkUQ5NqPHx3+k0S8c/oYwXICFSnijHN8yqxbjaMPD1ghetbe1IWTdJp+VR/m /eSYfTcrnHs97tEvPwjP4ZhtiiNYucWSJOkFBGUt1hk6/l63etPSfeVf+lcScq0hg0A+ tZcTMviHD8ftXn1eKzSN6KZ24YSb0aeOr7P1jnr9Ot09Lv0htRMOpBpXIBgk0JLZZ1sC VV6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732292801; x=1732897601; 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=tI/ul8ZfuzCLRKtKvNgdJwGLAJk7gXb7MrCiDeVXmB4=; b=wSTB1DZ6RjltT9W2BWez+/wSjnaqCCBcDPLZnhidIGlCMjh0f+plvceaVko3ZKSxUo krXHaFhtEBHf0Ad5yDUuGMkC8syMeDWhtN9d7lSOt8AmhSJvTjkN1g+9iFwFezB8ZB9q 9my+Lur5QWQSaPuhsbymINsBv64Vv6xc9Do5Y/O7bTVFxoA7HI1ZviV0Eefk4k4LrIjy i++fZwfRSsgUQSEzxs+P/URP5/vU2E4rXQnWZ5l6eMtqMex5jraoqx5myLyNAfYg5jGG //C+ikF267apILQNni28Zftkp3I1Ovc8uEBKKgmq92FF4h6FgslaetGHBqfYoDNR3Ocp oGSw== X-Gm-Message-State: AOJu0Yz9kVoAJkVN9j3PSQeMID1a9WwAZbxZP8nrGiw5+DgwCnx6t24z qEMc6bP/XUOCB5M5jLKCGuE/+7H16FIKU7o3Q11kDygmd3Z78PKG/w7mZTS8aSPSWmovVPV2Z+J eDyugyC9o8FDCeABMpvDcAgshX6Y= X-Gm-Gg: ASbGnctodYjuOk0xS4cu10RMlL5eTELZc7uDgBssh8dN0cEwKHXTjL+nxTYKR7m4vav HqjbRRcRlg3l95k1udg0pLviX/T6D4oMHI26IDgCZN2ZZ6qMV X-Google-Smtp-Source: AGHT+IH/5f39mwxH86r+5rUgTe6q7hyOD8ki3r+Dshz2c76+xi79M9v0ufxxUsWYRWHyslIxftjmjRhALISZFUdi2Oo= X-Received: by 2002:ad4:5dcf:0:b0:6cd:eeb4:4f73 with SMTP id 6a1803df08f44-6d450e7c124mr47317016d6.14.1732292801642; Fri, 22 Nov 2024 08:26:41 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jethish Jethish Date: Fri, 22 Nov 2024 21:56:30 +0530 Message-ID: Subject: Re: PostgreSQL Log Info To: "David G. Johnston" Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000016c9e0062782d984" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000016c9e0062782d984 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry guys, what I meant was to log the tuple returned count not the values to get printed in logs. On Fri, Nov 22, 2024, 9:46=E2=80=AFPM David G. Johnston wrote: > 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. > --00000000000016c9e0062782d984 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Sorry guys, what I meant was to log the tu= ple returned count not the values to get printed in logs.


On Fri= , Nov 22, 2024, 9:46=E2=80=AFPM David G. Johnston <david.g.johns= ton@gmail.com> wrote:
On Fri, Nov 22, 2024 at 12:32=E2=80=AFAM Jethish Jethish <jethish777@gmail.com> wrote:

If an select query is fired I need the query retu= rned values needs to be logged in my PostgreSQL log file.

Then the answer is no, and unlikely to become a feature anyone woul= d develop or that we'd accept.

A more innovative = solution is going to need to be thought up to satisfy=C2=A0the=C2=A0securit= y people that want to know what data was acquired=C2=A0from their system by= either their users or semi-privileged hackers (privileged exploits would l= ikely just disable such logging anyway).=C2=A0 The space of setting up a pr= oxy server in between clients and the PostgreSQL server is under-explored a= s a means by which to incorporate such functionality externally to the core= server.

David J.
--00000000000016c9e0062782d984--