| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Let's start talking features and "theme" for 9.4 |
| Date: | 2014-05-02 08:56:28 |
| Message-ID: | 1399020988.7224.3.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Fri, 2014-05-02 at 08:36 +0900, Michael Paquier wrote:
> On Fri, May 2, 2014 at 4:39 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> > but I am looking for, so in early next versions some interesting bgworkers
> > will be in core - scheduler, idle connection killer, multi CPU sorter, ...
> -1 for that. Those bgworkers things satisfy very specific needs (I
> implemented one of them in the list). I'd rather see a wiki page
> listing them properly and let each implementer maintain their code.
>
Completely agree with Michael. I see them just like FDWs. We don't add
some FDW in the core. Some are contrib modules, some are available
elsewhere. BgWorkers should be handled the same way.
> > So I am thinking, it should be marked as "other" feature this year.
> +1 for that. Dynamic background workers is a hacker feature.
+1
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-05-02 09:10:58 | Re: Let's start talking features and "theme" for 9.4 |
| Previous Message | Michael Paquier | 2014-05-01 23:36:20 | Re: Let's start talking features and "theme" for 9.4 |