| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Josh berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rename max_parallel_degree? |
| Date: | 2016-06-03 12:30:13 |
| Message-ID: | CAKFQuwaBbH53x+i0MbaFzBDh3DhAXPS7EzjpEGKVvPRW-6HzNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 3, 2016 at 8:20 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Jun 2, 2016 at 4:35 PM, Josh berkus <josh(at)agliodbs(dot)com> wrote:
> > I was assuming that we would have *both* per-operation and per-statement
> > limits. I can see reasons for having both, I can see why power users
> > would want both, but it's going to be overwhelming to casual users.
>
> I don't think so. I think the fact that this is per-gather-node
> rather than per-statement right now is basically a defect. Once we
> have a per-statement limit, I see no value in having the
> per-gather-node setting. So, yes, at that point, I would push to
> rename the GUC.
>
>
How big is the hazard of future-naming this and documenting the present
limitation? Is the casual user reading explains even going to be aware of
that particular implementation detail?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-06-03 12:34:47 | Re: Rename max_parallel_degree? |
| Previous Message | David G. Johnston | 2016-06-03 12:27:38 | Re: Prepared statements and generic plans |