| From: | diPhantxm <diphantxm(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Truncate logs by max_log_size |
| Date: | 2024-09-26 18:30:08 |
| Message-ID: | CA+E0NR4S+NC6+QHyY_vUuQZMzLhKqczMx-jJVqtjAxF6+=JwAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
I would like to suggest a patch to truncate some long queries. I believe
sometimes there is no need to log a query containing some gigabytes of
blob, for example. In patch a new parameter, named max_log_size, is
introduced. It defines the maximum size of logged query, in bytes.
Everything beyond that size is truncated.
Best regards,
Kirill Gavrilov
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-parameter-max_log_size-to-truncate-logs.patch | application/octet-stream | 4.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-09-26 18:57:21 | Re: Opinion poll: Sending an automated email to a thread when it gets added to the commitfest |
| Previous Message | Alvaro Herrera | 2024-09-26 17:52:03 | ALTER TABLE ONLY .. DROP CONSTRAINT on partitioned tables |