Message-ID: <6e38983d-924a-8dc3-eba6-66635ed4b4e9@timescale.com>
Date: Tue, 2 Aug 2022 11:42:03 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: Add LZ4 compression in pg_dump
Content-Language: en-US
To: Michael Paquier <michael@paquier.xyz>, gkokolatos@pm.me
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@lists.postgresql.org,
 Rachel Heaton <rachelmheaton@gmail.com>
References: <20220626155532.GA9311@telsasoft.com>
 <u7dLpRH_6r_rGyqNWHSDx2Wz5g1virAU3-f4XMC2BwiR81Tegqm4Sxtte0YAe77je9KVMa4jVxDNSt3XkYLYpyOoabCid1Bm7BZxwoitcmY=@pm.me>
 <YtjeUvZxIN+yIEMw@paquier.xyz>
From: Jacob Champion <jchampion@timescale.com>
In-Reply-To: <YtjeUvZxIN+yIEMw@paquier.xyz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/6e38983d-924a-8dc3-eba6-66635ed4b4e9%40timescale.com>
Precedence: bulk

This entry has been waiting on author input for a while (our current
threshold is roughly two weeks), so I've marked it Returned with
Feedback.

Once you think the patchset is ready for review again, you (or any
interested party) can resurrect the patch entry by visiting

    https://commitfest.postgresql.org/38/3571/

and changing the status to "Needs Review", and then changing the
status again to "Move to next CF". (Don't forget the second step;
hopefully we will have streamlined this in the near future!)

Thanks,
--Jacob