6.0.0-beta1
7/8/25

[#10774] Postgresql bytea escaping
Summary Postgresql bytea escaping
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Resolved
Priority 3. High
Owners slusarz (at) horde (dot) org
Requester slusarz (at) horde (dot) org
Created 11/17/2011 (4982 days ago)
Due
Updated 11/17/2011 (4982 days ago)
Assigned
Resolved 11/17/2011 (4982 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
11/17/2011 07:40:50 AM Git Commit Comment #3 Reply to this comment
Changes have been made in Git for this ticket:

Bug #10774: Hex encoding only works with Postgres 9.0+

  2 files changed, 21 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/da887f93403436577150890b2f4909781676345d
11/17/2011 06:04:04 AM Michael Slusarz Assigned to Michael Slusarz
State ⇒ Resolved
 
11/17/2011 06:03:51 AM Git Commit Comment #2 Reply to this comment
Changes have been made in Git for this ticket:

[mms] Greatly reduce memory usage when working with binary data in 
PostgreSQL (Bug #10774).

  2 files changed, 2 insertions(+), 17 deletions(-)
http://git.horde.org/horde-git/-/commit/657116cbc6886d71a07d9ad60868c58622b31980
11/17/2011 05:24:31 AM Michael Slusarz Comment #1
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Postgresql bytea escaping
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
We are currently using the "escape" format.  This has the potential to 
increase the data size by 5-6 times: \\xxx for one character, with the 
additional overhead that the backslashes may themselves need to be 
escaped.

Instead use hex escaping, the preferred way, which should only 
increase payload size 2 times:

http://www.postgresql.org/docs/9.0/static/datatype-binary.html

Saved Queries