Re: [PoC PATCH] Parallel dump to /dev/null

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Michael Banck <michael(dot)banck(at)credativ(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PoC PATCH] Parallel dump to /dev/null
Date: 2018-02-02 04:22:24
Message-ID: 20180202042224.GC3267@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-02-02 05:06:50 Re: [HACKERS] Creating backup history files for backups taken from standbys
Previous Message Michael Paquier 2018-02-02 04:16:22 Re: [HACKERS] taking stdbool.h into use