Relocate the non-english locale section to the bottom as it appears to no longer be relevant.

jwp · jwp · commit e103bb8ebb7b · 2020-12-08T10:53:12.000-07:00
diff --git a/postgresql/documentation/gotchas.rst b/postgresql/documentation/gotchas.rst
@@ -5,14 +5,6 @@ It is recognized that decisions were made that may not always be ideal for a
 given user. In order to highlight those potential issues and hopefully bring
 some sense into a confusing situation, this document was drawn.
 
-Non-English Locales
--------------------
-
-Many non-english locales are not supported due to the localization of the severity field
-in messages and errors sent to the client. Internally, py-postgresql uses this to allow
-client side filtering of messages and to identify FATAL connection errors that allow the
-client to recognize that it should be expecting the connection to terminate.
-
 Thread Safety
 -------------
 
@@ -112,3 +104,11 @@ This exception is raised by a generic processing routine whose functionality
 is abstract in nature, so the message is abstract as well. It essentially means
 that a tuple in the sequence given to the loading method had too many or too few
 items.
+
+Non-English Locales
+-------------------
+
+In the past, some builds of PostgreSQL localized the severity field of some protocol messages.
+`py-postgresql` expects these fields to be consistent with their english terms. If the driver
+raises strange exceptions during the use of non-english locales, it may be necessary to use an
+english setting in order to coax the server into issueing familiar terms.
