| 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 (5124 days ago) |
| Due | |
| Updated | 11/17/2011 (5124 days ago) |
| Assigned | |
| Resolved | 11/17/2011 (5124 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
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
State ⇒ Resolved
[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
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Postgresql bytea escaping
Type ⇒ Bug
State ⇒ Unconfirmed
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