Guido Neitzer wrote:
> ----8<--------8<--------8<--------8<--------8<--------8<----
> 2.2.1. Unstructured Header Field Bodies
>
>
> Some field bodies in this standard are defined simply as
> "unstructured" (which is specified below as any US-ASCII characters,
> except for CR and LF) with no further restrictions. These are
> referred to as unstructured field bodies. Semantically,
> unstructured
> field bodies are simply to be treated as a single line of characters
> with no further processing (except for header "folding" and
> "unfolding" as described in section 2.2.3).
>
> ----8<--------8<--------8<--------8<--------8<--------8<----
So see what "folding" means. Section 2.2.3 says
2.2.3. Long Header Fields
Each header field is logically a single line of characters comprising
the field name, the colon, and the field body. For convenience
however, and to deal with the 998/78 character limitations per line,
the field body portion of a header field can be split into a multiple
line representation; this is called "folding". The general rule is
that wherever this standard allows for folding white space (not
simply WSP characters), a CRLF may be inserted before any WSP. For
example, the header field:
Subject: This is a test
can be represented as:
Subject: This
is a test
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
