Re: Verify Option with pg_dump

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Verify Option with pg_dump
Date: 2016-11-30 13:33:05
Message-ID: 20161130133305.wzkknrljqg7bdoo7@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 30, 2016 at 01:11:58PM +0000, Howard News wrote:

> > You can try to suitably combine "pg_dump --format=plain" with
> > "tee" and "md5sum" such that the output stream is diverted to
> > both a file and a pipe-into-CRC-algorithm and eventually
> > compare the pipe's sum with the sum generated from the file.
> >
> > But the better solution might be to stream to a filesystem
> > that verifies disk writes immediately. Or to a suitable RAID
> > array.
> Thanks for this info Karsten. I will look into using "tee". As a matter of
> interest, why does the format need to be plain?

Actually, any of the formats producing a _single_ file right
away are likely to work. So, any but "directory", I guess.

> Regarding the filesystem solution, the dump is currently written to a HP
> RAID 10 array with an NTFS partition. What filesystems / raid arrays have
> this ability?

If you can't trust your RAID 10 (1 meaning mirrored) to
actually store what you told it to you've got problems beyond
somehow verifying a pg_dump.

Regards,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Timoteo Blanco 2016-11-30 13:42:20 select function alias
Previous Message Howard News 2016-11-30 13:18:06 Re: Traffic monitor postgres