Christophe Pettus: All Your GUCs in a Row: The geqo Family
All seven are user context, so any of them can be set per session, per role, or per database. The reason to take them as a group is that six of the seven only matter if you have already lost. The one that matters is geqo_threshold, and what it controls is whether the other six ever come into play at all.
- ▪All seven are user context, so any of them can be set per session, per role, or per database.
- ▪The reason to take them as a group is that six of the seven only matter if you have already lost.
- ▪The one that matters is geqo_threshold, and what it controls is whether the other six ever come into play at all.
2 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Christophe Pettus: All Your GUCs in a Row: from_collapse_limit — Planet PostgreSQL
Planet PostgreSQL files mainly under programming. We currently carry 25 of its stories.
Opening excerpt (first ~120 words) tap to expand
2026-07-25 11 min PostgreSQL All Your GUCs in a Row: The geqo Family Seven parameters, one feature, and a reasonable goal of never using any of them. geqo, geqo_threshold, geqo_effort, geqo_pool_size, geqo_generations, geqo_selection_bias, and geqo_seed all configure the Genetic Query Optimizer, an alternative join-order search that PostgreSQL falls back to when a query has too many relations for the regular planner to handle exhaustively. All seven are user context, so any of them can be set per session, per role, or per database. The reason to take them as a group is that six of the seven only matter if you have already lost. The one that matters is geqo_threshold, and what it controls is whether the other six ever come into play at all.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
