management systems have it as well.
+ Values of type character are physically padded
+ with spaces to the specified width n>, and are
+ stored and displayed that way. However, the padding spaces are
+ treated as semantically insignificant. Trailing spaces are
+ disregarded when comparing two values of type character,
+ and they will be removed when converting a character value
+ to one of the other string types. Note that trailing spaces
+ are> semantically significant in
+ character varying and text values.
+
+
The storage requirement for data of these types is 4 bytes plus the
actual string, and in case of character plus the
There are no performance differences between these three types,
apart from the increased storage size when using the blank-padded
- type.
+ type. While character(n>) has performance
+ advantages in some other database systems, it has no such advantages in
+
PostgreSQL. In most situations
+ text or character varying should be used
+ instead.
*
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/utils/adt/varchar.c,v 1.103 2003/11/29 19:51:59 pgsql Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/adt/varchar.c,v 1.104 2004/02/01 06:27:48 tgl Exp $
*
*-------------------------------------------------------------------------
*/
bpcharlen(PG_FUNCTION_ARGS)
{
BpChar *arg = PG_GETARG_BPCHAR_P(0);
+ int len;
- /* optimization for single byte encoding */
- if (pg_database_encoding_max_length() <= 1)
- PG_RETURN_INT32(VARSIZE(arg) - VARHDRSZ);
+ /* get number of bytes, ignoring trailing spaces */
+ len = bcTruelen(arg);
+
+ /* in multibyte encoding, convert to number of characters */
+ if (pg_database_encoding_max_length() != 1)
+ len = pg_mbstrlen_with_len(VARDATA(arg), len);
- PG_RETURN_INT32(
- pg_mbstrlen_with_len(VARDATA(arg), VARSIZE(arg) - VARHDRSZ)
- );
+ PG_RETURN_INT32(len);
}
Datum