From: | Karthik Krishnakumar <karthikk(at)zohocorp(dot)com> |
---|---|
To: | "Michaeldba" <Michaeldba(at)sqlexec(dot)com> |
Cc: | "pgsql-admin" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Prepared statements generating a lot of temp files. |
Date: | 2023-03-23 09:59:17 |
Message-ID: | 1870de3f764.b57db35951182.3515927566054675220@zohocorp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
thanks - checked with the devs and it does look like the application is doing some sort of a bulk insert, and at the moment it cannot be changed to use "COPY FROM".
will limiting bulk inserts to match the work_mem(assuming this is the guc that is used in this case) reduce this disk activity?
thanks,
karthik
---- On Thu, 23 Mar 2023 14:43:19 +0530 <Michaeldba(at)sqlexec(dot)com> wrote ---
Look at the size of the bind variables and also whether you are doing bulk inserts
Sent from my iPad
On Mar 23, 2023, at 5:10 AM, Karthik Krishnakumar <mailto:karthikk(at)zohocorp(dot)com> wrote:
Hi admins,
I am analyzing temp files being generated using pg_badger.
Under "queries generating the most temporary files", I am finding insert/update queries (via prepared statements) writing a lot of data to temp files.
I am trying to figure why inserts are generating such temp files.
Why are inserts/updates generating temp files?
what can be done to avoid this ?
thanks,
karthik
From | Date | Subject | |
---|---|---|---|
Next Message | MichaelDBA | 2023-03-23 10:03:11 | Re: Prepared statements generating a lot of temp files. |
Previous Message | Michaeldba@sqlexec.com | 2023-03-23 09:13:19 | Re: Prepared statements generating a lot of temp files. |