| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Default setting for enable_hashagg_disk |
| Date: | 2020-06-20 22:04:02 |
| Message-ID: | 20200620220402.GZ17995@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Thu, Jun 11, 2020 at 01:22:57PM -0700, Jeff Davis wrote:
> > think the names you suggested quite fit, but the idea to use a more
> > interesting GUC value might help express the behavior. Perhaps making
> > enable_hashagg a ternary "enable_hashagg=on|off|avoid_disk"? The word
> > "reject" is too definite for the planner, which is working with
> > imperfect information.
>
> I renamed enable_hashagg_disk to hashagg_avoid_disk_plan, which I think
> satisfies the concerns raised here. Also in 92c58fd9.
I think this should be re-arranged to be in alphabetical order
https://www.postgresql.org/docs/devel/runtime-config-query.html
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2020-06-21 16:21:02 | wrong output column title in example |
| Previous Message | Alvaro Herrera | 2020-06-19 17:10:37 | Re: Add A Glossary |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-06-20 23:06:27 | Re: [HACKERS] Restricting maximum keep segments by repslots |
| Previous Message | Tomas Vondra | 2020-06-20 21:57:23 | Re: Resetting spilled txn statistics in pg_stat_replication |