Re: [HACKERS] Custom compression methods

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, David Steele <david(at)pgmasters(dot)net>, Ildus Kurbangaliev <i(dot)kurbangaliev(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [HACKERS] Custom compression methods
Date: 2021-02-05 15:56:38
Message-ID: 20210205155638.GJ7450@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

+ * If the called has passed an invalid slot then create a new slot.
*caller

+ * Slot for storing the modified tuple, incase the target attribute's
*in case

Could you comment on the patch I sent on Jan 30 ? I think it would be squished
into 0001.
> Subject: [PATCH v21 2/7] Add default_toast_compression GUC

Also, what about the idea to add HIDE_COMPRESSAM ? Right now, your patch
changes a great many regression tests, and I doubt many people are going to try
to look closely to verify the differences, now, or when setting a non-default
compression method.

Also, I think we may want to make enable-lz4 the default *for testing
purposes*, now that the linux and BSD environments include that.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-02-05 16:07:53 Re: [HACKERS] Custom compression methods
Previous Message Stephen Frost 2021-02-05 15:54:25 Re: Fuzz testing COPY FROM parsing