Re: pg_do_encoding_conversion glitch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_do_encoding_conversion glitch
Date: 2008-11-11 03:02:18
Message-ID: 9249.1226372538@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Do you have a proposal for a different API, or do you just want to
>> improve the comment for the function? Bear in mind that a lot of the
>> callers do know the string length, and so we shouldn't impose an
>> unnecessary strlen() operation on those cases.

> We already have the following comment, so I think a new comment is
> not needed.
> | In the case of no conversion, src is returned.

I added a few more lines just to help people out --- in digging around
earlier today, there seemed to be a few places that hadn't been very
careful about this.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-11-11 03:12:43 Re: db_user_namespace, md5 and changing passwords
Previous Message Tom Lane 2008-11-11 02:46:05 Re: Patch for ISO-8601-Interval Input and output.