public inbox for [email protected]
help / color / mirror / Atom feedFrom: Muhammad Ikram <[email protected]>
To: sud <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Insert query performance
Date: Tue, 20 Aug 2024 15:59:13 +0500
Message-ID: <CAGeimVqjCKdUp2fNYS_2FpE1OyXiue=dRu43MHzcG_SD7Kxw1Q@mail.gmail.com> (raw)
In-Reply-To: <CAD=mzVVtnELmUbTGVecmjGZ8HwiVvhj7V5XBPR5Woref0BN=Rg@mail.gmail.com>
References: <CAD=mzVXZiDmAsTE1XiXnq1DFHM22uwnD8jckmBN_bTakk3u2AQ@mail.gmail.com>
<CAGeimVqF+2vAwbMRznGvbAWs=1u+4zLkZ11irO3yuBP6sLmPow@mail.gmail.com>
<CAD=mzVVtnELmUbTGVecmjGZ8HwiVvhj7V5XBPR5Woref0BN=Rg@mail.gmail.com>
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 <[email protected]> wrote:
>
> On Mon, Aug 19, 2024 at 1:25 PM Muhammad Ikram <[email protected]> wrote:
>
>> Hi Sud,
>>
>> Please make following change in your postgresql.conf file
>>
>> log_statement = 'all'
>>
>>
> Will this put all the internal sql query or the recursive query entries in
> 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.
>
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Insert query performance
In-Reply-To: <CAGeimVqjCKdUp2fNYS_2FpE1OyXiue=dRu43MHzcG_SD7Kxw1Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox