Re: [PoC PATCH] Parallel dump to /dev/null - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PoC PATCH] Parallel dump to /dev/null
Date
Msg-id 20180202042224.GC3267@paquier.xyz
Whole thread Raw
In response to [PoC PATCH] Parallel dump to /dev/null  (Michael Banck <michael.banck@credativ.de>)
Responses Re: [PoC PATCH] Parallel dump to /dev/null  (Michael Banck <michael.banck@credativ.de>)
Re: [PoC PATCH] Parallel dump to /dev/null  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
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.

FWIW, I use this trick as well in some test deployments.  Now, those
deployments happen in places where I want the checks to warn me, so the
time it takes is not really an issue generally.  Do folks here think
that speedups would be worth it?  Say to make the operation shorter on
production systems for example.  A lengthy pg_dump bloats data for a
longer time, so I can buy that shorter times may help, though I think
that hearing from other folks is necessary as well.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] taking stdbool.h into use
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Creating backup history files for backups taken fromstandbys