Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 54299b9

Browse files
committed
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
1 parent de61a9c commit 54299b9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3819,13 +3819,13 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
38193819
</para>
38203820

38213821
<para>
3822-
IEEE Std 802-2001 specifies the second shown form (with hyphens)
3822+
IEEE Standard 802-2001 specifies the second form shown (with hyphens)
38233823
as the canonical form for MAC addresses, and specifies the first
3824-
form (with colons) as the bit-reversed notation, so that
3825-
08-00-2b-01-02-03 = 01:00:4D:08:04:0C. This convention is widely
3824+
form (with colons) as used with bit-reversed, MSB-first notation, so that
3825+
08-00-2b-01-02-03 = 10:00:D4:80:40:C0. This convention is widely
38263826
ignored nowadays, and it is relevant only for obsolete network
38273827
protocols (such as Token Ring). PostgreSQL makes no provisions
3828-
for bit reversal, and all accepted formats use the canonical LSB
3828+
for bit reversal; all accepted formats use the canonical LSB
38293829
order.
38303830
</para>
38313831

0 commit comments

Comments
 (0)