> because of specs of blockchain component.
Based on this schema ( https://grisha.org/blog/2017/12/15/blockchain-and-postgres/ AND https://github.com/blkchain/pg_blkchain )
and
IF (your) blockchain component is using BYTEA everywhere ( binary data type : https://www.postgresql.org/docs/9.6/datatype-binary.html )
THEN ( imho) you can't expect lot of space saving.
> Rhel 7.6. . ... There is a requirement for data compression
IF (your) blockchain component is using BYTEA everywhere ( binary data type : https://www.postgresql.org/docs/9.6/datatype-binary.html )
THEN ( imho) you can't expect lot of space saving.
> Rhel 7.6. . ... There is a requirement for data compression
On RedHat (>=7.5) you can test the new VDO compression layer
it is mentioned few weeks ago: "... VDO compression for tables that are less update intensive. "
on Postgres level - you can enable the "wal_compression"
regards,
Imre
Shital A <brightuser2019@xxxxxxxxx> ezt írta (időpont: 2019. aug. 5., H, 8:30):
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.
