Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1pmZN7-0007o4-9p
	for pgsql-docs@arkaria.postgresql.org; Wed, 12 Apr 2023 12:14:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1pmZN5-0008Uv-Pj
	for pgsql-docs@arkaria.postgresql.org; Wed, 12 Apr 2023 12:14:43 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1pmZN5-0008Um-ID
	for pgsql-docs@lists.postgresql.org; Wed, 12 Apr 2023 12:14:43 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1pmZN2-002R8f-QX
	for pgsql-docs@lists.postgresql.org; Wed, 12 Apr 2023 12:14:42 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 33CCEc7w826012;
	Wed, 12 Apr 2023 08:14:38 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
cc: Julien Rouhaud <rjuju123@gmail.com>, eric.mutta@gmail.com,
        pgsql-docs@lists.postgresql.org
Subject: Re: Should 'sum(mvf)' read 'sum(mcv)'...?
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>
Comments: In-reply-to Daniel Gustafsson <daniel@yesql.se>
	message dated "Wed, 12 Apr 2023 13:14:31 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <826010.1681301678.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Apr 2023 08:14:38 -0400
Message-ID: <826011.1681301678@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Archived-At: 
 <https://www.postgresql.org/message-id/826011.1681301678%40sss.pgh.pa.us>
Precedence: bulk

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 a=
ttached
> 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