| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: character confusion |
| Date: | 2010-03-05 21:19:23 |
| Message-ID: | 7296.1267823963@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
> Just noticed something odd with a column of type "char". According to
> the docs (and the way my old PG ran), the character data-type is
> blank-padded. I'm not seeing that on one of my current machines (8.3.8)
> or, perhaps I'm going blind on Friday. Was the definition of char changed?
No; what you're forgetting is that length() doesn't count padding spaces
in char(N) input. Try octet_length() if you want to be convinced that
the spaces are there.
Was your "old" PG pre-8.0? We changed that quite a long time ago.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2010-03-05 22:07:12 | Re: For Loop using row_data to increase performance |
| Previous Message | Wang, Mary Y | 2010-03-05 20:59:02 | Re: Restore Data Encountered the ERROR: literal carriage return found in data Error |