Re: Eager aggregation, take 3
От | Richard Guo |
---|---|
Тема | Re: Eager aggregation, take 3 |
Дата | |
Msg-id | CAMbWs4_SLP-Qw8DMsY3Gc56GmLiMNWXnf5g1BwMFGq09BJRx-A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Eager aggregation, take 3 (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Thu, Oct 9, 2025 at 11:13 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Richard Guo <guofenglinux@gmail.com> writes: > > On Wed, Oct 8, 2025 at 11:45 PM Robert Haas <robertmhaas@gmail.com> wrote: > >> For what it's worth, I also don't like that field name. I'm not sure > >> what to propose instead, but I don't think apply_at is very clear. > > This field represents the set of relids at which partial aggregation > > is applied. So how about naming it partial_agg_designated_relids? > > That feels a bit verbose, though. How about partial_agg_relids or, > > for brevity, agg_relids instead? > I might be missing a subtlety here, but how about > "apply_aggregation_at" or "apply_partial_agg_at"? > > I don't think including "relids" in the field name adds anything, > given the field's declared type and comments. Fair point. 'agg' seems better to me than 'aggregation' when used in a name: it's shorter, and it's unlikely anyone would interpret it as anything other than "aggregation". I kind of wonder whether we need to include 'partial' in the name. Given the context, it seems very clear that we're referring to partial aggregation rather than final aggregation. So I'm weighing between "apply_partial_agg_at" and "apply_agg_at". - Richard
В списке pgsql-hackers по дате отправления: