On Thu, Feb 6, 2025 at 6:46 AM Marcos Pegoraro <mar...@f10.com.br> wrote:
> And obviously, if you don't know the purpose of that GUC, you'll have to > read the entire paragraph to understand it. > Objective here is to those ones who know what it is, but don't > remember its default. > That seems a somewhat arbitrary goal for us to optimize for. I just read through https://www.postgresql.org/docs/current/runtime-config-query.html and while perhaps some of the defaults could be slightly more prominent, none of them took more than a second of brain-cpu-power to find. The only one that threw me off was join_collapse_limit, which really should just state the eight. So for me a -1 for major changes, but a weak +1 to improving some individual items. Cheers, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support
