| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bytea_output output of base64 |
| Date: | 2017-02-24 02:48:44 |
| Message-ID: | 053017e1-ea48-4b80-2935-5680ed3ac74d@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/23/17 8:22 PM, Bruce Momjian wrote:
> I was just curious because it seems more compact than hex and many
> exchange formats use it, like SSL certificates and keys. I know you can
> encode() but I thought it might help make pg_dump output smaller.
It undoubtedly would make pg_dump smaller, though I'm not sure how much
that's worth since if you care at all about that you'll gzip it.
But, the other thing it might do is speed up COPY, especially on input.
Some performance tests of that might be interesting.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-24 02:48:54 | Re: Documentation improvements for partitioning |
| Previous Message | Michael Paquier | 2017-02-24 02:47:28 | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |