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 1tEWca-007vyS-Gv for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:35:04 +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 1tEWcZ-00AMWN-6Y for pgsql-general@arkaria.postgresql.org; Fri, 22 Nov 2024 16:35:03 +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 1tEWcY-00AMW4-S3 for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:35:02 +0000 Received: from mail-oa1-x2f.google.com ([2001:4860:4864:20::2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tEWcW-003JGg-P4 for pgsql-general@lists.postgresql.org; Fri, 22 Nov 2024 16:35:02 +0000 Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-29692ad4b42so1504039fac.3 for ; Fri, 22 Nov 2024 08:35:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732293299; x=1732898099; 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=dGUTdap6p6T3sDhX40fRbSwTZJSdcfS3E8C4f1QDtmY=; b=Iw9ljJQ+zeQx2Bk8qxZp0WQHW4tU22t2sIR6fNbEfW7w/YX99Sy14suobpxY+wKBdk hxaru37UNEypVxcq+uZp++Ps9kB8QVs3wXnpcVAQTbDvt0Q4eskxrer0gvULfJ7ez5Bl TZyhFoxFsLmLUHqVLLP0jsenSLLJIfMU8mdmFowNG+GaE8HUV2dJR/WjODcKqzHV0PvG zacvVWi2oZ88Ksvi+6xqChaUYyNsBXOJeuirvrm1vwepB1+9Pm1qWaQqownEWJZfr9dm GxvRRTaUHjQdD+FnX1L7Zt3IFA+vIfQ4MLcFD5pzmi7teG6/Q3wxeAQGmWFmjg+Jib1+ BBpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732293299; x=1732898099; 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=dGUTdap6p6T3sDhX40fRbSwTZJSdcfS3E8C4f1QDtmY=; b=dWT7JlkJQHYkQD+a0lcvYO7TvcXc4l1kfVWEPTuQicXUvzqEO+TVBNQCKB/wepYjDG PxZT5IIXvQB31aZNygsX+uFc8/tyubONeHQhdm9KC3jrgFr6bdzwtodqfq2CACjWX2Nf gkbReKePNdy0cIX931miPmBGAw4sSfoTZ0+x0atFGGfURuiDO1ed+d+jogEXkudlMMBI cwfsZul+TVvzuUST6FqIdSH0VbLHdoHiHUMXrRnLbwDL2C0t09YuvtoHuGeaAjqjDib7 P/u7ihTOjvKW0GwOo3jnsAcidkBC3XMhqAD7StyZEpHDY4LqU/jvO6/FhET5/AFDO6HL hh6w== X-Gm-Message-State: AOJu0YzD+UE8giHNvewxh7IGcGlFOa4Zt22gqTq8GermJY4hmuhzH1iJ clRnlgUL8KLMJYjkbQkHTikgGvpOmHeFGDH+wMdF6+wUNIrpf/t7Jscz/kdBxlWOjoDm1jZxZr1 XDRvmTOSVaINoI2HXEA/ippouTQQ= X-Gm-Gg: ASbGncutoVLZhzolK3Nl12UBF/EyDhfn7ufLkCrVMCoVitRgDk7AMv73FGm+uhprpR2 VhMe4w/ESWihP0WUb42SuuQLKxckhGwc= X-Google-Smtp-Source: AGHT+IGzUveNp3oMhU/hvxzxvoBw+xsX+r4LMv86jcvmL59q5fzlj4cMnyusxByDG4KC8IkX0OLiv9BW4vfSK2PliU0= X-Received: by 2002:a05:6870:956c:b0:297:285e:f948 with SMTP id 586e51a60fabf-297285efac4mr1801028fac.17.1732293298708; Fri, 22 Nov 2024 08:34:58 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Fri, 22 Nov 2024 09:34:18 -0700 Message-ID: Subject: Re: PostgreSQL Log Info To: Jethish Jethish Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000b769db062782f67b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b769db062782f67b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Nov 22, 2024 at 9:26=E2=80=AFAM Jethish Jethish wrote: > Sorry guys, what I meant was to log the tuple returned count not the > values to get printed in logs. > That too is a no. Though more because is just doesn't seem useful enough to expend effort on designing and implementing something. There is a work-around in that you could enable auto-explain with analyze and read the actuals from that. David J. --000000000000b769db062782f67b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Nov 22, 2024 at 9:26=E2=80=AFAM Jethish Jethish &l= t;jethish777@gmail.com> wrot= e:

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

That too is a no.=C2=A0 Though more because = is just=C2=A0doesn't seem useful enough to expend effort on designing a= nd implementing=C2=A0something.

There is a work-around= in that you could enable auto-explain with analyze and read the actuals=C2= =A0from that.

David J.

--000000000000b769db062782f67b--