From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: less log level for success dynamic background workers for 9.5 |
Date: | 2015-06-23 01:07:06 |
Message-ID: | CA+TgmobKUpo8KbCaUQLgeAKSmEnCruhyrYXhg0g1xkjiET68ww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 22, 2015 at 8:19 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 6/14/15 12:25 AM, Pavel Stehule wrote:
>> I am working on scheduler extension for 9.5. It use bgworkers
>> intensively for any task. This is reason, why I need to decrease a log
>> level - and I am thinking so parallel computing needs it due high number
>> of created and finished workers.
>>
>> It should be fixed in 9.5 - because it is limiting factor for bgworkers
>> usage in 9.5.
>
>
> Anything ever happen with this? I agree that LOG is to high for reporting
> most (if not all) of these things.
I think we should consider having a flag for this behavior rather than
changing the behavior across the board.
But then again, maybe we should just change it.
What do others think?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-06-23 01:14:36 | Re: less log level for success dynamic background workers for 9.5 |
Previous Message | Robert Haas | 2015-06-23 01:05:52 | Re: pg_stat_*_columns? |