| From: | Mladen Gogala <gogala(dot)mladen(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Force re-compression with lz4 |
| Date: | 2021-10-19 13:24:40 |
| Message-ID: | 3bef5bb7-a1c9-95f8-cfe4-98fa0d96e7c6@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/18/21 11:01, Adrian Klaver wrote:
> ot sure how much this applies to the Postgres usage of lz4. As I
> understand it, this is only used internally for table compression.
> When using pg_dump compression gzip is used. Unless you pipe plain
> text output through some other program.
This applies when using a 3rd party commercial backup tool with
deduplication. You'd be surprised how many people do that. One tool to
backup them all, one tool to find them and on the LTO cartridge backup
them. I apologize for this cheesy paraphrase of Tolkien, but I couldn't
resist. Long story short, for the 3rd party backup tools LZO4
compression will yield better deduplication ratios than other forms of
compression, thereby saving you space.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Saurav Sarkar | 2021-10-19 17:15:23 | Connection queuing by connection pooling libraries |
| Previous Message | Alban Hertroys | 2021-10-19 09:29:51 | Re: Where is the tsrange() function documented? |