lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10e99b47-2978-4dbf-90f0-750c7fbb6064@wiesinger.com>
Date: Wed, 22 Jan 2025 07:10:18 +0100
From: Gerhard Wiesinger <lists@...singer.com>
To: "Kiselev, Oleg" <okiselev@...zon.com>, "Theodore Ts'o" <tytso@....edu>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Transparent compression with ext4 - especially with zstd

On 22.01.2025 01:19, Kiselev, Oleg wrote:
> MySQL, MariaDB and PostgreSQL do their own, schema and page-size aware compression.  Why not let the databases do this?  They are in a better position to do it and trade off the costs where and when it matters to them.

Hello Oleg,

Thnx for the input. For PostgreSQL: AFAIK compression only works for 
larger tables (e.g. >2kB) and it looks like it doesn't work for my usecase.

But will have a deeper look into it.

Ciao,

Gerhard


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ