| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fix bgworkers in EXEC_BACKEND |
| Date: | 2012-12-27 18:45:32 |
| Message-ID: | CA+U5nM+FNeM1ifs1KfobOnQh0PgdPQzgJdo7_NFUCGr3=+pNLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27 December 2012 18:36, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Simon,
>
> * Simon Riggs (simon(at)2ndQuadrant(dot)com) wrote:
>> I admire your forward thinking on that; yes, that could cause
>> problems. But even then, we would be admitting that nobody now gets a
>> valid value of MaxBackends, which sounds like it might be a problem in
>> itself.
>
> I agree that the current implementation could lead to problems/confusion
> for contrib module authors, if they're doing something with MaxBackends.
I can't see any problems myself and am happy with Heikki's proposal to
accept that restriction, since other workarounds are possible.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-12-27 18:49:13 | Re: fix bgworkers in EXEC_BACKEND |
| Previous Message | Simon Riggs | 2012-12-27 18:42:12 | Re: Event Triggers: adding information |