| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14473: Parallel query aborts with too many connections |
| Date: | 2016-12-23 12:57:05 |
| Message-ID: | CAA4eK1+FGDU17voS669j3Rb5Tmb3ZgVPtN-1fJh5WdxmXGjc-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Dec 23, 2016 at 3:47 PM, Steven Winfield
<Steven(dot)Winfield(at)cantabcapital(dot)com> wrote:
>
> OTOH, if parallel queries could be made tolerant of workers failing to start
> then there wouldn't be as much of an issue (though doubtless this is easier
> said than done!)
>
I think it is difficult to decide which errors parallel query be made
tolerant. I also don't think it is advisable to make parallel query
handle some errors. I think here DBA should carefully use the
connection limits. I think it might be okay to add a note in parallel
query docs to indicate that parallel workers use database connection.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steven Winfield | 2016-12-23 14:58:48 | Re: BUG #14473: Parallel query aborts with too many connections |
| Previous Message | Michael Paquier | 2016-12-23 11:44:19 | Re: BUG #14473: Parallel query aborts with too many connections |