From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: eric.mutta@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Should 'sum(mvf)' read 'sum(mcv)'...?
Date: Wed, 12 Apr 2023 08:14:38 -0400
Message-ID: <826011.1681301678@sss.pgh.pa.us> (raw)
In-Reply-To: <63973B1A-BFE6-46B4-A6E3-3B098ECAC351@yesql.se>
References: <166112292492.654.5377188452604176150@wrigleys.postgresql.org>
<20220822074837.dy4i5t7n5xmbhjbw@jrouhaud>
<255694.1661173111@sss.pgh.pa.us>
<63973B1A-BFE6-46B4-A6E3-3B098ECAC351@yesql.se>
Daniel Gustafsson <daniel@yesql.se> writes:
> I was inclined to spell it out as mcv_frequencies but we use xxx_freqs
> elsewhere on the same page so keeping it consistent seems better. The attached
> does this as well as adding mcf/mcv as acronyms as previously mentioned (since
> they are both tagged as <acronym>).
mcv_freqs looks good. I'd write the glossary entries as singular
(Most Common Frequency, Most Common Value) since our typical usage
is to pluralize them at the point of use ("MCVs"). Also, just
expanding the acronym doesn't seem that helpful. Maybe more like
MCF
Most Common Frequency, that is the frequency associated
with some Most Common Value
MCV
Most Common Value, one of the values appearing most often
within a particular table column
regards, tom lane
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: tgl@sss.pgh.pa.us, daniel@yesql.se, rjuju123@gmail.com, eric.mutta@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Should 'sum(mvf)' read 'sum(mcv)'...?
In-Reply-To: <826011.1681301678@sss.pgh.pa.us>
* 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