| From: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: Logging parallel worker draught |
| Date: | 2023-04-28 08:11:20 |
| Message-ID: | f4962c2a-69a6-8c1d-b79a-37c59785f2b0@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/22/23 13:06, Amit Kapila wrote:
> I don't think introducing a GUC for this is a good idea. We can
> directly output this message in the server log either at LOG or DEBUG1
> level.
Hi,
Sorry for the delayed answer, I was away from my computer for a few
days. I don't mind removing the guc, but I would like to keep it at the
LOG level. When I do audits most client are at that level and setting it
to DEBUG1 whould add too much log for them on the long run.
I'll post the corresponding patch asap.
--
Benoit Lobréau
Consultant
http://dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-04-28 08:49:45 | Re: Testing autovacuum wraparound (including failsafe) |
| Previous Message | Denis Laxalde | 2023-04-28 08:08:15 | Re: Add PQsendSyncMessage() to libpq |