From: Scott Marlowe <scott.marlowe@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Shaul Dar <shauldar@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Compression in PG
Date: Sun, 1 Nov 2009 08:57:42 -0700
Message-ID: <dcc563d10911010757o3cededc0x9859ef2c47002919@mail.gmail.com> (raw)
In-Reply-To: <162867790911010656m37b315dbp41761a014745b9e4@mail.gmail.com>
References: <234efe30911010651k6cf3d398t9d61e560d57b52b7@mail.gmail.com>
<162867790911010656m37b315dbp41761a014745b9e4@mail.gmail.com>
On Sun, Nov 1, 2009 at 7:56 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> 2009/11/1 Shaul Dar <shauldar@gmail.com>:
>> Hi,
>>
>> I have several long text fields in my DB that I would love to compress
>> (descriptions, URLs etc). Can you tell me what options exists in PG
>> (+pointers please), typical effect on space and run time?
>
> Hello
>
> You can do nothing. PostgreSQL compresses data automatically
>
> http://www.postgresql.org/docs/8.4/interactive/storage-toast.html
Well you can pick a strategy. But yeah, there's not much for the
average user to do really.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, pavel.stehule@gmail.com, shauldar@gmail.com
Subject: Re: Compression in PG
In-Reply-To: <dcc563d10911010757o3cededc0x9859ef2c47002919@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox