Values to be inserted into a table are coerced to the destination column's data type according to the following steps.
Query Target Type Resolution
Check for an exact match with the target.
Otherwise, try to coerce the expression to the target type. This will succeed if the two types are known binary-compatible, or if there is a conversion function. If the expression is an unknown-type literal, the contents of the literal string will be fed to the input conversion routine for the target type.
If the target is a fixed-length type (e.g. char or varchar declared with a length) then try to find a sizing function for the target type. A sizing function is a function of the same name as the type, taking two arguments of which the first is that type and the second is an integer, and returning the same type. If one is found, it is applied, passing the column's declared length as the second parameter.
Example 5-6. character Storage Type Conversion
For a target column declared as character(20) the following query ensures that the target is sized correctly:
tgl=> CREATE TABLE vv (v character(20)); CREATE tgl=> INSERT INTO vv SELECT 'abc' || 'def'; INSERT 392905 1 tgl=> SELECT v, length(v) FROM vv; v | length ----------------------+-------- abcdef | 20 (1 row)
What has really happened here is that the two unknown literals are resolved to text by default, allowing the || operator to be resolved as text concatenation. Then the text result of the operator is coerced to bpchar ("blank-padded char", the internal name of the character data type) to match the target column type. (Since the parser knows that text and bpchar are binary-compatible, this coercion is implicit and does not insert any real function call.) Finally, the sizing function bpchar(bpchar, integer) is found in the system catalogs and applied to the operator's result and the stored column length. This type-specific function performs the required length check and addition of padding spaces.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.