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 1tEPe2-007Btq-4n for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 09:08:06 +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 1tEPe0-006rIR-St for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 09:08:04 +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 1tEPe0-006rII-HN for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 09:08:04 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEPdu-003FUs-JV for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 09:08:03 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3e5ffbc6acbso1163203b6e.3 for ; Fri, 22 Nov 2024 01:07:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732266476; x=1732871276; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=3H5tzLFKTS8F3Z6NpYhbrSgE6aLvAfXsNsHMeIzSOcQ=; b=fhUg02pA+7nS6jVi9KFuGsP4oXHLzNZwqKSHULGcJJvgoRAnoKZES+jaeysB9usi5l xAhW97tWxjPbyvpEf3WPJoLBAZyxtsHt1H8usqdNf/8ICRBWaBz8tobIpSf2GdhPXnZr CwB4FnipnRVodNdeBYpCJMxkS/L/m1PqDSI0lo6B85dwTomamAvgrtVpvv6Y7LcLctWx hLtrKXT6SOiOpI8fHPl3vbjtAfIlRCQEsCImSOQERk+5ybix3P9Kms+AqAgQtfdR8iF7 nyldwo/1iCRqiI0ItN99bRe8XHM8JQ6elU7gUvLn/gjOwfQKrDK3ww1c/f/Y9eu6yI+a HuOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732266476; x=1732871276; h=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=3H5tzLFKTS8F3Z6NpYhbrSgE6aLvAfXsNsHMeIzSOcQ=; b=DGJ1alb4yUqVMWUH1esqsQD+xHNZDwOsKYbAOmpei857//IPb5zbt+J0v57d9BJaY6 e3FmCPWpi9sMHp6K+jTU9ToqsLkeubiAqNErQnMbawwXx/6S8qAMoO7uFtXc6lOpWxIX MkQ+DVWoROyJGsL0NiGB67WZf5TgHTnajvE7uPkslgNJN45CVAQo5grGdyR86esB6exQ OqfBixQIAjXG+rjsHqnT5rW/hUIW3xI/S83ELFDXjZGTIQL9h7ZqqNop4Zsv0clAhDhV nM0mQLP4ufa+MAHN0B+xojSqzifUwyZ7pBUDg4bJLIPAJCQXYkSPMK7jgA2qHNL48cMv 7Niw== X-Gm-Message-State: AOJu0Yxx/6LqutDs3byZNE5LztV8Hl26wzvy/Sb/3UutRecMK4tAF6p0 TLp1baUE5+yBaXWw3fnNn7c4Rg2IgyqV3Sk8myffL65QzV7CO8PVHSGWY2KV+JH8JB2tEC8S7Qe Gwy3/GvJKNHjDH1BMUl/mBs2kOuzpbJ4v X-Gm-Gg: ASbGnctPbbrTF1NRoIsCpm2DL2xdve6UB/liyt8rtiaQ1jENCeAFiT1AZAi+Xw/FyEG /VEIgVsTymDrBSsmBAOkpBcYXqnJ86T8M X-Google-Smtp-Source: AGHT+IELhN8ZZ9/zIRm/syvsqG3SSsbn3s1/hCCmtE7yLwq2Mtj65JlHYKzyL0faD+Nfekc45YGYoZkZPkHhY3xINK4= X-Received: by 2002:a05:6808:23d6:b0:3e5:fd33:36a6 with SMTP id 5614622812f47-3e915b32466mr2484977b6e.35.1732266475774; Fri, 22 Nov 2024 01:07:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Fri, 22 Nov 2024 04:07:44 -0500 Message-ID: Subject: Re: PostgreSQL Log Info To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000f1e99106277cb7b7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f1e99106277cb7b7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Isn't "I need the query returned values" the purpose of the client application? On Fri, Nov 22, 2024 at 2:32=E2=80=AFAM Jethish Jethish wrote: > Hi David, > > If an select query is fired I need the query returned values needs to be > logged in my PostgreSQL log file. > > > For example if a select query returns 5 rows I need the same in the log > file > > On Fri, Nov 22, 2024, 10:49=E2=80=AFAM David G. Johnston < > david.g.johnston@gmail.com> wrote: > >> On Thursday, November 21, 2024, Jethish Jethish >> wrote: >>> >>> Is it possible to log the rows returned by a query in the PostgreSQL >>> logs? >>> >> >> As a practical matter, no. That said, given one can get row contents >> into the server log in various ways, what is the use case for why this >> capability is thought to be needed? >> >> David J. >> > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000f1e99106277cb7b7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Isn't "I need the query returned= values" the purpose of the client application?

On Fri, Nov 22, 2024 at= 2:32=E2=80=AFAM Jethish Jethish <jethish777@gmail.com> wrote:

Hi David,

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


For example if a select query ret= urns 5 rows I need the same in the log file=C2=A0


On Fri= , Nov 22, 2024, 10:49=E2=80=AFAM David G. Johnston <d= avid.g.johnston@gmail.com> wrote:
On Thursday, November 21, 2024, Jethish Jethish &l= t;jethish777@gmail.com> wrote:
Is = it possible to log the rows returned by a query in the PostgreSQL logs?

As a practical matter, no.=C2=A0 T= hat said, given one can get row contents into the server log in various way= s, what is the use case for why this capability is thought to be needed?

David J.=C2=A0


--
Death to <Redacted>, and butter sauce.Don't boil me, I'm still alive.
<Redacted> lobs= ter!
--000000000000f1e99106277cb7b7--