| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Compression In Postgresql 9.6 |
| Date: | 2019-08-05 07:11:53 |
| Message-ID: | 82708249-ab53-cca8-1d1d-3ca45fa6dde5@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 8/5/19 1:30 AM, 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.
Column-level compression? Because some data just doesn't compress well.
>
> 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?
Are your tables partitioned?
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2019-08-05 08:09:59 | Re: How to check if a field exists in NEW in trigger |
| Previous Message | Shital A | 2019-08-05 06:30:14 | Compression In Postgresql 9.6 |