| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Anders Hammarquist <iko(at)strakt(dot)com>, pgsql-bugs(at)postgresql(dot)org, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Subject: | Re: Bug #728: Interactions between bytea and character encoding |
| Date: | 2002-08-04 05:55:10 |
| Message-ID: | 200208040555.g745tAL02963@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Joe Conway wrote:
> Tom Lane wrote:
> > Ah. So the issue is that ANALYZE tries to do textin(byteaout(...))
> > in order to produce a textual representation of the most common value
> > in the BYTEA column, and apparently textin feels that the string
> > generated by byteaout is not legal text. While Joe says that the
> > problem has gone away in CVS tip, I'm not sure I believe that.
>
> I didn't either, except I tried it and it worked ;-) But you're
> undoubtedly correct that there are other cases which would break the
> current code.
Does this mean we don't have to esacpe >0x7f when inputting bytea
anymore?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-04 06:29:44 | Re: Bug #728: Interactions between bytea and character encoding |
| Previous Message | Joe Conway | 2002-08-04 05:26:28 | Re: Bug #728: Interactions between bytea and character encoding |