Re: Add LZ4 compression in pg_dump
От | Justin Pryzby |
---|---|
Тема | Re: Add LZ4 compression in pg_dump |
Дата | |
Msg-id | 20221120172611.GQ11463@telsasoft.com обсуждение исходный текст |
Ответ на | Re: Add LZ4 compression in pg_dump (Georgios Kokolatos <gkokolatos@protonmail.com>) |
Ответы |
Re: Add LZ4 compression in pg_dump
|
Список | pgsql-hackers |
On Fri, Aug 05, 2022 at 02:23:45PM +0000, Georgios Kokolatos wrote: > Thank you for your work during commitfest. > > The patch is still in development. Given vacation status, expect the next patches to be ready for the November commitfest. > For now it has moved to the September one. Further action will be taken then as needed. On Sun, Nov 06, 2022 at 02:53:12PM +0000, gkokolatos@pm.me wrote: > On Wed, Nov 2, 2022 at 14:28, Justin Pryzby <pryzby@telsasoft.com> wrote: > > Checking if you'll be able to submit new patches soon ? > > Thank you for checking up. Expect new versions within this commitfest cycle. Hi, I think this patch record should be closed for now. You can re-open the existing patch record once a patch is ready to be reviewed. The commitfest is a time for committing/reviewing patches that were previously submitted, but there's no new patch since July. Making a patch available for review at the start of the commitfest seems like a requirement for current patch records (same as for new patch records). I wrote essentially the same patch as your early patches 2 years ago (before postgres was ready to consider new compression algorithms), so I'm happy to review a new patch when it's available, regardless of its status in the cfapp. BTW, some of my own review comments from March weren't addressed. Please check. Also, in February, I asked if you knew how to use cirrusci to run checks on cirrusci, but the patches still had compilation errors and warnings on various OS. https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest/39/3571 -- Justin
В списке pgsql-hackers по дате отправления: