Re: Partial Mode in Aggregate Functions

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Partial Mode in Aggregate Functions
Date: 2026-03-01 13:25:20
Message-ID: CAB-JLwZtjy2gmLxu9L-kEKoKU16OSA8QA35=Vjy4vy-VraLKQw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em sex., 27 de fev. de 2026 às 22:58, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:

> I commented about the phrasing for this being not ideal for the target
>> audience of the functions reference page. Here's some other wording to
>> consider:
>
>
I sent this link to some colleagues and asked, "Tell me what 'Partial Mode'
means." Some are developers, some are DBAs, and some are just starting out.
Those who responded in less than 20 seconds obviously didn't read the
headers; they just deduced it by looking at the table title. And yes, some
said it related to aggregating data on fewer records. So, putting an
explanation in the header probably won't completely solve the problem,
since many people only look at the table, and if they can draw any
conclusions from it, they ignore the rest of the text.

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yura Sokolov 2026-03-01 14:20:25 Re: Fix bug in multixact Oldest*MXactId initialization and access
Previous Message David Rowley 2026-03-01 13:10:56 Re: More speedups for tuple deformation