| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Chris R(dot)" <chricki(at)gmx(dot)net> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5854: base64 decode returns bytea and no text |
| Date: | 2011-01-28 16:18:20 |
| Message-ID: | 201101281618.p0SGIKO20424@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Chris R. wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5854
> Logged by: Chris R.
> Email address: chricki(at)gmx(dot)net
> PostgreSQL version: 9.02
> Operating system: CentOS 5.5
> Description: base64 decode returns bytea and no text
> Details:
>
> There is a break in how pg9.0 handles decoding base64 encoded data.
>
> With PostgreSQL 8.4:
>
> select decode(encode('abc', 'base64'), 'base64');
> decode
> ----------
> \x616263
>
>
> With PostgreSQL 9.0:
>
> select decode(encode('abc', 'base64'), 'base64');
> decode
> ----------
> \x616263
>
>
> To get the old result, convert_from helps out:
> select convert_from(decode(encode('abc', 'base64'), 'base64'), 'UTF8');
>
> Still, shouldn't this be consistent with 8.x and 9.x?
Uh, they look the same to me. cut/paste error?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondrej Pachner | 2011-01-28 16:45:34 | BUG #5855: pgstat wait timeout |
| Previous Message | Tom Lane | 2011-01-28 16:17:28 | Re: BUG #5854: base64 decode returns bytea and no text |