From: Daniel Gustafsson <daniel@yesql.se>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Subject: Re: Consistency of units (bits vs bytes)
Date: Tue, 15 Nov 2022 11:15:51 +0100
References: <166845317039.635.6194510047097701846@wrigleys.postgresql.org>
To: troy@frericks.us,
 pgsql-docs@lists.postgresql.org
In-Reply-To: <166845317039.635.6194510047097701846@wrigleys.postgresql.org>
Message-Id: <A38B4156-5818-4F28-8AC1-CBAA48757026@yesql.se>
Archived-At: 
 <https://www.postgresql.org/message-id/A38B4156-5818-4F28-8AC1-CBAA48757026%40yesql.se>
Precedence: bulk

> On 14 Nov 2022, at 20:12, PG Doc comments form =
<noreply@postgresql.org> wrote:
>=20
> The following documentation comment has been logged on the website:
>=20
> Page: https://www.postgresql.org/docs/15/datatype-uuid.html
> Description:
>=20
> One can describe the size of datatypes in the common units of bits or =
bytes.
> It'd be desirable to be consistent. Please reference these two =
pages...=20
> https://www.postgresql.org/docs/current/datatype-numeric.html (data =
types
> sized in bytes)
> and
> https://www.postgresql.org/docs/current/datatype-uuid.html (data type =
sized
> in bits)

These are different things, the page with numeric types discuss the =
number of
bytes used to store the values.  UUIDs are defined in the RFC as 128-bit
identifiers, which is related to but not by definition the same as the =
space
used to store them in the database.

--
Daniel Gustafsson		https://vmware.com/