From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | ljb <ljb9832(at)pobox(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Gripe: bytea_output default => data corruption |
Date: | 2011-02-02 21:27:49 |
Message-ID: | 201102022127.p12LRnZ04134@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Bruce Momjian wrote:
> ljb wrote:
> > tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
> > > I think we should simply remove the description of *how* the escaping is
> > > performed, and state only that the function produces a suitably escaped
> > > literal string. Anything else is not future-proof, and could someday
> > > break the way this wording did.
> >
> > Perhaps it would be best to remove escaping details here. But the
> > description of PQescapeBytea() might need to be rewritten, too. Without
> > describing exactly what PQescapeByteaConn() does, it is hard to understand
> > what PQescapeBytea() does not do, and why it therefore "might give the
> > wrong results".
> >
> > I think the actual function behavior should be documented somewhere. Even
> > though it might change again.
>
> Based on this report, I have created the attached documentation patch
> which clarifies the libpq behavior for escaping bytea. I am planning to
> backpatch this to 9.0 as well.
My aplogies on the double-attachment. I am now attaching the right
verison.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/libpq.diff | text/x-diff | 3.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-02-02 23:10:00 | varname for GUC variables |
Previous Message | Bruce Momjian | 2011-02-02 21:25:52 | Re: [GENERAL] Gripe: bytea_output default => data corruption |