From 54299b9ce7ccea885c06d6833ec04b3b06a82788 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 3 Jun 2022 11:51:37 -0400
Subject: [PATCH] Doc: fix incorrect bit-reversal in example of macaddr
formatting.
Will Mortensen (minor additional copy-editing by me)
Discussion: https://postgr.es/m/CAMpnoC5Y6jiZHSA82FG+e_AqkwMg-i94EYqs1C_9kXXFc3_3Yw@mail.gmail.com
---
doc/src/sgml/datatype.sgml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index f7f6e1ee94..a623d67d7c 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -3819,13 +3819,13 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
</para>
<para>
- IEEE Std 802-2001 specifies the second shown form (with hyphens)
+ IEEE Standard 802-2001 specifies the second form shown (with hyphens)
as the canonical form for MAC addresses, and specifies the first
- form (with colons) as the bit-reversed notation, so that
- 08-00-2b-01-02-03 = 01:00:4D:08:04:0C. This convention is widely
+ form (with colons) as used with bit-reversed, MSB-first notation, so that
+ 08-00-2b-01-02-03 = 10:00:D4:80:40:C0. This convention is widely
ignored nowadays, and it is relevant only for obsolete network
protocols (such as Token Ring). PostgreSQL makes no provisions
- for bit reversal, and all accepted formats use the canonical LSB
+ for bit reversal; all accepted formats use the canonical LSB
order.
</para>