On Tue, Jun 15, 2021 at 11:14:56AM -0500, Justin Pryzby wrote: > You're right, I hadn't though this through all the way. > There's precedent if the default is non-static (wal_sync_method). > > But I think yes/on/true/1 should be a compatibility alias for a static thing, > and then the only option is pglz. > > Of course, changing the default to LZ4 is still a possibility.
We have not reached yet a conclusion with the way we are going to parameterize all that, so let's adapt depending on the feedback. For now, I am really interested in this patch set, so I am going to run some tests of my own and test more around the compression levels we have at our disposals with the proposed algos. From I'd like us to finish with here is one new algorithm method, able to cover a large range of cases as mentioned upthread, from low-CPU/low-compression to high-CPU/high-compression. It does not seem like a good idea to be stuck with an algo that only specializes in one or the other, for example. -- Michael
signature.asc
Description: PGP signature
