pgsql: Document encode(bytea, 'escape')'s behavior correctly.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Document encode(bytea, 'escape')'s behavior correctly.
Date: 2013-03-29 03:15:33
Message-ID: E1ULPmv-0006Na-Ue@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Document encode(bytea, 'escape')'s behavior correctly.

I changed this in commit fd15dba543247eb1ce879d22632b9fdb4c230831, but
missed the fact that the SGML documentation of the function specified
exactly what it did. Well, one of the two places where it's specified
documented that --- probably I looked at the other place and thought
nothing needed to be done. Sync the two places where encode() and
decode() are described.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/9ad27c215362df436f8c16f1aace923011f31be4

Modified Files
--------------
doc/src/sgml/func.sgml | 20 ++++++++++++--------
1 files changed, 12 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-03-29 03:15:34 pgsql: Document encode(bytea, 'escape')'s behavior correctly.
Previous Message Tom Lane 2013-03-29 02:09:38 pgsql: Must check indisready not just indisvalid when dumping from 9.2