Re: bytea_output output of base64

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Kenneth Marshall <ktm(at)rice(dot)edu>, David Fetter <david(at)fetter(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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 20:23:52
Message-ID: b7b1f30e-b4c4-96b6-ea62-e9dc98d60594@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/24/17 7:44 AM, Kenneth Marshall wrote:
> Like David suggests,
> if you want compact, run it through lz4/gzip/lzop...for a much better size
> return.

Speaking of which; any bytea where you care about this is likely to live
in an already compressed state in toast. ISTM it would be valuable if we
had a way to just spit out the raw compressed data (or a text-safe
version of that), at least for COPY's purposes...
--
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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2017-02-24 20:25:34 Re: [PROPOSAL] Temporal query processing with range types
Previous Message Jim Nasby 2017-02-24 20:20:42 Re: FYI: git worktrees as replacement for "rsync the CVSROOT"