From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PoC PATCH] Parallel dump to /dev/null |
Date: | 2018-02-02 10:25:41 |
Message-ID: | 21A17278-81A8-480F-886C-05D89340918B@yandex-team.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
Michael, thanks for the patch!
> 2 февр. 2018 г., в 9:22, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> написал(а):
>
> On Thu, Feb 01, 2018 at 02:24:46PM +0100, Michael Banck wrote:
>> dumping a database to /dev/null via pg_dump is (AFAIK) one recommended
>> way to check for corruption. However, dumping to /dev/null is currently
>> not supported in directory mode which makes it not possible to dump to
>> /dev/null in parallel.
>
> Do folks here think that speedups would be worth it?
I've seen backup verification via COPY TO to /dev/null in production. These copies were parallelized on the side of verification script.
Not sure this counts for feature or against it.
Best regards, Andrey Borodin.
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2018-02-02 10:33:14 | Re: [HACKERS] Add support for tuple routing to foreign partitions |
Previous Message | Andres Freund | 2018-02-02 10:08:40 | Re: JIT compiling with LLVM v9.0 |