Re: Add LZ4 compression in pg_dump
От | gkokolatos@pm.me |
---|---|
Тема | Re: Add LZ4 compression in pg_dump |
Дата | |
Msg-id | 4ZDVII-_kusch7xndcrTUt7OPSuQWQGX7n8rqp625Hdv6DijBjWZ38gjhxLSzPu8M_Dka-50eeKCiCU_dOdawwpv06dZtwGroYE9dHlIBLc=@pm.me обсуждение исходный текст |
Ответ на | Re: Add LZ4 compression in pg_dump (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: Add LZ4 compression in pg_dump
Re: Add LZ4 compression in pg_dump |
Список | pgsql-hackers |
------- Original Message ------- On Wednesday, January 25th, 2023 at 7:00 PM, Justin Pryzby <pryzby@telsasoft.com> wrote: > > > On Wed, Jan 25, 2023 at 03:37:12PM +0000, gkokolatos@pm.me wrote: > > While looking at this, I realized that commit 5e73a6048 introduced a > regression: > > @@ -3740,19 +3762,24 @@ ReadHead(ArchiveHandle *AH) > > - if (AH->compression != 0) > > - pg_log_warning("archive is compressed, but this installation does not support compression -- no data will be available"); > + if (AH->compression_spec.algorithm == PG_COMPRESSION_GZIP) > > + pg_fatal("archive is compressed, but this installation does not support compression"); > > Before, it was possible to restore non-data chunks of a dump file, even > if the current build didn't support its compression. But that's now > impossible - and it makes the code we're discussing in RestoreArchive() > unreachable. Nice catch! Cheers, //Georgios > -- > Justin
В списке pgsql-hackers по дате отправления: