Re: zstd compression for pg_dump
От | Jacob Champion |
---|---|
Тема | Re: zstd compression for pg_dump |
Дата | |
Msg-id | CAAWbhmgm8yzKLnwK8-Wj-nhYo3R0AvLF6FSX-Pgo=062hGz4JA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: zstd compression for pg_dump (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: zstd compression for pg_dump
|
Список | pgsql-hackers |
On Sat, Mar 4, 2023 at 8:57 AM Justin Pryzby <pryzby@telsasoft.com> wrote: > pryzbyj=# CREATE TABLE t1 AS SELECT i,array_agg(j) FROM generate_series(1,444)i,generate_series(1,99999)j GROUP BY 1; > $ ./src/bin/pg_dump/pg_dump -d pryzbyj -Fc -Z zstd:long=1 |wc -c > 82023 > $ ./src/bin/pg_dump/pg_dump -d pryzbyj -Fc -Z zstd:long=0 |wc -c > 1048267 Nice! I did some smoke testing against zstd's GitHub release on Windows. To build against it, I had to construct an import library, and put that and the DLL into the `lib` folder expected by the MSVC scripts... which makes me wonder if I've chosen a harder way than necessary? Parallel zstd dumps seem to work as expected, in that the resulting pg_restore output is identical to uncompressed dumps and nothing explodes. I haven't inspected the threading implementation for safety yet, as you mentioned. And I still wasn't able to test :workers, since it looks like the official libzstd for Windows isn't built for multithreading. That'll be another day's project. --Jacob
В списке pgsql-hackers по дате отправления: