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 1tEM58-006tIn-Tr for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 05:19:50 +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 1tEM57-005PlL-Hl for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 05:19:49 +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 1tEM57-005PlD-6Z for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 05:19:49 +0000 Received: from mail-ua1-x92b.google.com ([2607:f8b0:4864:20::92b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEM54-003Duh-MC for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 05:19:48 +0000 Received: by mail-ua1-x92b.google.com with SMTP id a1e0cc1a2514c-856f9be0389so566729241.1 for ; Thu, 21 Nov 2024 21:19:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732252784; x=1732857584; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=e0ApXYweNeb+cMEDcFeZiOtWpszf6xWISM+/Z9/zez0=; b=JmAjuNX5N7+H+Gj2joOA82aY/zGZvUnBS5MXSW9eVaPUa4kl2Y86RhPpffahvAQXyh oD+t7xFYCKinsP6BkZ6NPK7fEg051B1zLfLnV7LjTkEUICcdyHCNFx0UJPrcPlUng/og gcn7TEuwz9YhmnnbIUZd7tkbXF7jBGjPPeYFqa9K0DyfAm4DUno8KmtUcfnGBc2Gj9d4 LdB9sRiCBt+FXtaW55jfX1jmgdMH/es3jxLlzU5or6NcboSQTwSquUchBXyAuK7QcfUF pDn/wIcURFkJNrptbJuAbSWtDcsCJeWasg906ezwtS8y8B0YvKP41Y57crpCzOjGSPyD YACg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732252784; x=1732857584; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=e0ApXYweNeb+cMEDcFeZiOtWpszf6xWISM+/Z9/zez0=; b=I7wvLingkxld2qV06IC/tRQZvTWWyWMLeU+IYsD6ibBakEo9hUfhvoQcEDYPj2Pom+ iEn+bGm2bTOJwnKyL+5xnepQW3gQaQxCgQ8RAozQCuNNghOeE5VtccRwpiRJ1gu/c1uw X0/NG8XkKwjlvq5v4RRMvynED5jTFBktmSWKbrZVg+SWfmMtysy/pyLmc6wAKFjTkVGZ lAmfgF4JlY7+oBBSgFTLoGLFAT7Smvv1FXdJxr5nqelnoY4OKvB1VoHSngSAyn89GD3J ISeg4RIYV85V4WMhDXY0r9A/n0ilMNCqeW/wVFwNh1nyhyfJ6iA46vQ16+8lyo5ALKX6 N3qw== X-Gm-Message-State: AOJu0YwepMJpMpCtFfpVh9OKrhEPLTurgTQyqDtiZMAhXkeRf0KWT9y/ NxbnbEmFtpDRMFbpI1V7E8y3v5RG1QrmzKSQRqhyuzHStFf/ovLqJGCt5YU6+a77JQe/BE0wcTL utGZBD0MySpOIMQa+SZr9NpuvuDU= X-Gm-Gg: ASbGncseP9Bw76who+GBM7yC7+Mw6Cv+CC48clPms6dvajsxMxDCeC+J6hX8M1UR3fY pT0OD2j8PjCJF7wHcYHXbse4Mk4ipNmU= X-Google-Smtp-Source: AGHT+IFc/ZTSQr2idb+TXlRTcyPwPHSy/NM5+E4oCFyXZQMnsRbuyUbKCSRWXeOG6fsa6yLInQclN3uuWIK3HOeGbKQ= X-Received: by 2002:a05:6102:1612:b0:4a4:950a:cb1f with SMTP id ada2fe7eead31-4addcea80c0mr2060688137.22.1732252784510; Thu, 21 Nov 2024 21:19:44 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6214:5e96:b0:6c3:6781:f2ca with HTTP; Thu, 21 Nov 2024 21:19:43 -0800 (PST) In-Reply-To: References: From: "David G. Johnston" Date: Thu, 21 Nov 2024 22:19:43 -0700 Message-ID: Subject: Re: PostgreSQL Log Info To: Jethish Jethish Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000e1d3960627798717" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e1d3960627798717 Content-Type: text/plain; charset="UTF-8" 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. --000000000000e1d3960627798717 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thursday, November 21, 2024, Jethish Jethish <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 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.=C2=A0
--000000000000e1d3960627798717--