MIME-Version: 1.0
References: <CAD=mzVXZiDmAsTE1XiXnq1DFHM22uwnD8jckmBN_bTakk3u2AQ@mail.gmail.com>
 <CAGeimVqF+2vAwbMRznGvbAWs=1u+4zLkZ11irO3yuBP6sLmPow@mail.gmail.com> <CAD=mzVVtnELmUbTGVecmjGZ8HwiVvhj7V5XBPR5Woref0BN=Rg@mail.gmail.com>
In-Reply-To: <CAD=mzVVtnELmUbTGVecmjGZ8HwiVvhj7V5XBPR5Woref0BN=Rg@mail.gmail.com>
From: Muhammad Ikram <mmikram@gmail.com>
Date: Tue, 20 Aug 2024 15:59:13 +0500
Message-ID: <CAGeimVqjCKdUp2fNYS_2FpE1OyXiue=dRu43MHzcG_SD7Kxw1Q@mail.gmail.com>
Subject: Re: Insert query performance
To: sud <suds1434@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000868ae206201b5135"
Archived-At: <https://www.postgresql.org/message-id/CAGeimVqjCKdUp2fNYS_2FpE1OyXiue%3DdRu43MHzcG_SD7Kxw1Q%40mail.gmail.com>
Precedence: bulk

--000000000000868ae206201b5135
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

It will record all statements in logs. If you are concerned about query
times then you may use pg_stat_statements.


Muhammad Ikram


On Tue, 20 Aug 2024 at 12:19, sud <suds1434@gmail.com> wrote:

>
> On Mon, Aug 19, 2024 at 1:25=E2=80=AFPM Muhammad Ikram <mmikram@gmail.com=
> wrote:
>
>> Hi Sud,
>>
>> Please make following change in your postgresql.conf file
>>
>> log_statement =3D 'all'
>>
>>
> Will this put all the internal sql query or the recursive query entries i=
n
> the pg_stats_statement view which we can analyze then? And also to debug
> issues in the production will it be a good idea to set it for a few times
> and then turn it off or it can have significant performance overhead.
>

--000000000000868ae206201b5135
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">It will record all statements in logs. If you are concern=
ed about query times then you may use pg_stat_statements.</div><div dir=3D"=
auto"><br clear=3D"all"><br clear=3D"all"><div dir=3D"auto"><div dir=3D"ltr=
" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"=
ltr"><div>Muhammad Ikram<br><br></div></div></div></div></div><div><br></di=
v><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Tue, 20 Aug 2024 at 12:19, sud &lt;<a href=3D"mailto:suds1434@gmail.com=
">suds1434@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Mon, Aug 19, 2024 at 1:25=E2=80=AFPM =
Muhammad Ikram &lt;<a href=3D"mailto:mmikram@gmail.com" target=3D"_blank">m=
mikram@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr">Hi Sud,<div><br></div><div>Please make fol=
lowing change in your postgresql.conf file</div><div><br></div><div>log_sta=
tement =3D &#39;all&#39;=C2=A0<br></div><div><br></div></div></blockquote><=
div><br></div><div>Will this put all the internal sql query or the recursiv=
e query entries in the pg_stats_statement view which we can analyze then? A=
nd also to debug issues in the production will it be a good idea to set it =
for a few times and then turn it off or it can have significant=C2=A0perfor=
mance overhead.</div></div></div>
</blockquote></div></div>

--000000000000868ae206201b5135--