| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "lsliang" <lsliang(at)pconline(dot)com(dot)cn> |
| Cc: | "pgsql-docs" <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: about value storage |
| Date: | 2011-09-06 15:52:32 |
| Message-ID: | 7708.1315324352@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
"lsliang" <lsliang(at)pconline(dot)com(dot)cn> writes:
> http://www.postgresql.org/docs/9.0/interactive/typeconv-query.html
> example shows:
> CREATE TABLE vv (v character(20));
> INSERT INTO vv SELECT 'abc' || 'def';
> SELECT v, length(v) FROM vv;
> v | length
> ----------------------+--------
> abcdef | 20
> (1 row)
> but my test show not like this :
Hmm, looks like that example was overlooked when we changed the behavior
years ago:
http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=f27976c85b1fb9002727cce65b9f9567e158f754
Given the context, we should change it to use octet_length().
Will fix, thanks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-09-06 16:40:54 | Re: Migration page is out of date |
| Previous Message | Tom Lane | 2011-09-06 15:19:45 | Re: Couple document fixes |