Re: Compression In Postgresql 9.6

From: Kenneth Marshall <ktm(at)rice(dot)edu>
To: Shital A <brightuser2019(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Compression In Postgresql 9.6
Date: 2019-08-05 12:31:20
Message-ID: 20190805123120.GB17132@aart.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Aug 05, 2019 at 12:00:14PM +0530, Shital A wrote:
> Hello,
>
> Need inputs on below:
>
> We are working on a setting up a new highly transactional (tps 100k) OLTP
> system for payments using blockchain and postgresql 9.6 as DB on Rhel 7.6.
> Postgres version is 9.6 and not latest because of specs of blockchain
> component.
>
> There is a requirement for data compression on DB level. Please provide
> your inputs on how this can be best achieved.
>
> Checked in-build Toast, it compressed the data provided exceed the 2kb
> pagesize? If the data values are small and even if there are billion
> records they wont be compressed, this is what I understood.
>
> Are there any suggestions of compressing older data irrespective of row
> size transparently?
>
> Thanks.

Hi,

On RHEL/Centos you can use VDO filesystem compression to make an archive
tablespace to use for older data. That will compress everything.

Regards,
Ken

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2019-08-05 13:22:41 Re: Compression In Postgresql 9.6
Previous Message PegoraroF10 2019-08-05 12:07:58 why toasted is created when domain is used ?