| From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
|---|---|
| To: | sud <suds1434(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Insert query performance |
| Date: | 2024-08-20 10:59:13 |
| Message-ID: | CAGeimVqjCKdUp2fNYS_2FpE1OyXiue=dRu43MHzcG_SD7Kxw1Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)gmail(dot)com> wrote:
>
> On Mon, Aug 19, 2024 at 1:25 PM Muhammad Ikram <mmikram(at)gmail(dot)com> 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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-08-20 11:43:13 | Re: Insert query performance |
| Previous Message | sud | 2024-08-20 07:19:12 | Re: Insert query performance |