| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: outfuncs.c utility statement support |
| Date: | 2017-06-14 15:49:24 |
| Message-ID: | CA+TgmoZHdEhZkDOx9xkQ6PaKy-UGtBYdUBnsS0KTpH_pLb7NNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 13, 2017 at 11:59 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> So this seems to be a pretty basic bug. Some node fields of type char
>> may be zero, and so printing them as a zero byte just truncates the
>> whole output string. This could be fixed by printing chars like strings
>> with the full escaping mechanism. See attached patch.
>
> +1. I've been meaning to report about
> zero-byte-truncating-the-whole-output-string thing for some time now.
I've been bitten by this, too.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Barai | 2017-06-14 15:50:12 | Re: GSoC 2017 weekly progress reports (week 2) |
| Previous Message | Ants Aasma | 2017-06-14 15:41:43 | Re: WIP: Data at rest encryption |