Re: PostGreSQL and zlib

From: "Hubert FONGARNAND" <informatique(dot)internet(at)fiducial(dot)fr>
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>, "Arnaud Balandras" <a(dot)balandras(at)fiducial(dot)fr>
Subject: Re: PostGreSQL and zlib
Date: 2007-10-25 11:49:57
Message-ID: 1193312997.10966.8.camel@hublinux.fidudev.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The problem is that for TOAST columns :
"The compression technique used is a fairly simple and very fast member
of the LZ family of compression techniques. See
src/backend/utils/adt/pg_lzcompress.c for the details."
With such function you could choose you compression algorithm and
compression level...

Another question : does this TOAST code works for all type of data, like
TEXT (in our case)

Le jeudi 25 octobre 2007 à 11:03 +0100, Gregory Stark a écrit :

> "Hubert FONGARNAND" <informatique(dot)internet(at)fiducial(dot)fr> writes:
>
> > I'm sure it's very easy to implement as a C function that would call zlib
> >
> > Is there already an implementation of such things?
>
> Not that I'm aware though you might look at pgcrypto. Good crypto has to
> compress first so there may be a possibility of just doing the compression.
>
> Postgres also will automatically try to compress data like byteas if the
> record is larger than 2kB (1/4 of the block size if you've changed the block
> size). So you may not have to do anything if you're just looking to save space
> on disk.
>
_______________________________________________
Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.
Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.
Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-10-25 12:26:47 Re: 8.3 GSS Issues
Previous Message Simon Riggs 2007-10-25 11:35:04 Re: order by in cursor declaration does not allow update