On Wed, Nov 15, 2017 at 4:09 AM, Ildus Kurbangaliev <i.kurbangal...@postgrespro.ru> wrote: > So in the next version of the patch I can just unlink the options from > compression methods and dropping compression method will not affect > already compressed tuples. They still could be decompressed.
I guess I don't understand how that can work. I mean, if somebody removes a compression method - i.e. uninstalls the library - and you don't have a way to make sure there are no tuples that can only be uncompressed by that library - then you've broken the database. Ideally, there should be a way to add a new compression method via an extension ... and then get rid of it and all dependencies thereupon. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company