Re: Table/Parition Level Compression in Postgres

From: Jagmohan Kaintura <jagmohan(at)tecorelabs(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Table/Parition Level Compression in Postgres
Date: 2022-02-16 12:46:30
Message-ID: CA+cYFtsLETZt1cH25wOPpGerdCNssHGrhZJwRVJXzMiRca2tZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Laurenz

Means that is what I am thinking even right now if we can move the
partition to another tablespace and have file system level compression.

Apart from this do we have any other solution or strategy which I can try
to implement?

On Wed, Feb 16, 2022 at 6:13 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Wed, 2022-02-16 at 18:10 +0530, Jagmohan Kaintura wrote:
> > We have a requirement where we wanted to keep the partitions holding the
> old data into compressed
> > format and the partition having the current data in the non-compressed
> format.
> > While looking over the compression aspects in Pg 14 we have some
> compression introduced for the column level with some compression methods.
> > Is there any other way using which we can compress the partitions data
> which can be even moved to different tablespace.
> > We have a implementation where we wanted to keep the 80% old data in the
> compressed format as we have millions of processed CDRs.
>
> How about a second tablespace on a file system that compresses files?
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>

--
*Best Regards,*
Jagmohan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Carsten Klein 2022-02-16 13:27:36 Strange results when casting string to double
Previous Message Laurenz Albe 2022-02-16 12:43:39 Re: Table/Parition Level Compression in Postgres