pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Davis <pgsql@j-davis.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Default setting for enable_hashagg_disk
Date: Thu, 09 Apr 2020 11:25:56 -0700
Message-ID: <ff9fdc4072e3be732ba9fd582f27982daecc4e43.camel@j-davis.com> (raw)
In-Reply-To: <20200409172404.GR2228@telsasoft.com>
References: <9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com>
	<20200407223900.GT2228@telsasoft.com>
	<20200409114855.h4hh7e2wt77p56sv@development>
	<20200409172404.GR2228@telsasoft.com>

On Thu, 2020-04-09 at 12:24 -0500, Justin Pryzby wrote:
> Also.. there's no such thing as enable_groupagg?  Unless I've been
> missing out
> on something.

I thought about adding that, and went so far as to make a patch. But it
didn't seem right to me -- the grouping isn't what takes the time, it's
the sorting. So what would the point of such a GUC be? To disable
GroupAgg when the input data is already sorted? Or a strange way to
disable Sort?

> Because HashAgg plans which used to run fine (because they weren't
> prevented
> from overflowing work_mem) might now run poorly after spilling to
> disk (because
> of overflowing work_mem).

It's probably worth a mention in the release notes, but I wouldn't word
it too strongly. Typically the performance difference is not a lot if
the workload still fits in system memory.

Regards,
	Jeff Davis







view thread (91+ messages)  latest in thread

Message-ID: <ff9fdc4072e3be732ba9fd582f27982daecc4e43.camel@j-davis.com>
Permalink:  ../ff9fdc4072e3be732ba9fd582f27982daecc4e43.camel@j-davis.com/
Also on:    postgresql.org/message-id/ff9fdc4072e3be732ba9fd582f27982daecc4e43.camel@j-davis.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pgsql@j-davis.com, pryzby@telsasoft.com, tomas.vondra@2ndquadrant.com, pgsql-hackers@postgresql.org
  Subject: Re: Default setting for enable_hashagg_disk
  In-Reply-To: <ff9fdc4072e3be732ba9fd582f27982daecc4e43.camel@j-davis.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox