| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log bloating with shortlife bgworkers? |
| Date: | 2015-05-15 20:15:37 |
| Message-ID: | CA+TgmobBBnGB8ExF2T2wfcFbZpPKt0mwYmdVun7pOfZmcs8Y+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 15, 2015 at 2:04 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I am planning to use short living bg workers. I was little bit surprised so
> any start and finish does entry in log. Is there any plan to decrease a log
> level for these purposes?
Parallel query is going to hit that issue, too. I imagine we'll do
something about it at some point. Maybe add a flag that reduces the
log level to DEBUG1 or DEBUG2.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-15 20:15:57 | Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL); |
| Previous Message | Robert Haas | 2015-05-15 20:14:10 | Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL); |