Re: Bug #728: Interactions between bytea and character encoding - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Bug #728: Interactions between bytea and character encoding
Date
Msg-id 200208040555.g745tAL02963@candle.pha.pa.us
Whole thread Raw
In response to Re: Bug #728: Interactions between bytea and character encoding  (Joe Conway <mail@joeconway.com>)
List 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@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-bugs by date:

Previous
From: Joe Conway
Date:
Subject: Re: Bug #728: Interactions between bytea and character encoding
Next
From: Joe Conway
Date:
Subject: Re: Bug #728: Interactions between bytea and character encoding