bytea escaping

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joe Conway" <joseph(dot)conway(at)home(dot)com>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: bytea escaping
Date: 2001-08-28 02:21:51
Message-ID: 13683.998965311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joe Conway" <joseph(dot)conway(at)home(dot)com> writes:
> ... is there a good reason that byteaout
> octal escapes all non-printable characters?

Well, AFAICS it *has to* escape nulls (zero bytes). Whether it escapes
more stuff is a matter of taste once you accept that.

What we really need to have to make bytea more useful is direct read and
write functions that don't require any escaping (a la large object
lo_read/lo_write).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2001-08-28 02:29:46 Re: Link to bug webpage
Previous Message Joe Conway 2001-08-28 02:20:33 Re: Upcoming events