Also this
https://en.wikipedia.org/wiki/Silent_data_corruption#Countermeasures
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
On Wed, Nov 30, 2016 at 01:53:21PM +, Howard News wrote:
> 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
>
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
On Wed, Nov 30, 2016 at 01:11:58PM +, 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
On 30/11/2016 12:27, Karsten Hilbert 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
On Wed, Nov 30, 2016 at 12:00:07PM +, Howard News wrote:
> recently I had problems with a corrupt pg_dump file. The problem with the
> file was due to a faulty disk. The trouble with this is that I was unaware
> of the disk problem and the pg_dump file corruption so I did not have a full
>
Hi,
recently I had problems with a corrupt pg_dump file. The problem with
the file was due to a faulty disk. The trouble with this is that I was
unaware of the disk problem and the pg_dump file corruption so I did not
have a full valid backup. In order to reduce the chances of this I was
