On 4/19/2017 9:24 AM, Alexandre wrote:
2) We dont use RAID.
so just a direct attached single disk drive? is it perchance a
'desktop' type disk? those often have dodgy write buffering and lie
about writes (saying they are complete when they are just in a volatile
ram buffer). sometimes
On Wed, 19 Apr 2017 13:25:41 -0300, Alexandre
wrote:
> :
>But there is no solution for [file corruption]?
The only solutions are to guard against it: make frequent backups and
make use of safety mechanisms in Postgresql and in the OS.
Postgresql logs (WAL) intended changes
It appears to be just one table I'm trying to backup without that table.
But there is no solution for this kind of error?
On Wed, Apr 19, 2017 at 1:11 PM, Moreno Andreo
wrote:
> Il 19/04/2017 17:49, Vick Khera ha scritto:
>
> 1) restore from backup
> 2) fix whatever
1) We have a backup but its from the last month, I will try to backup the
data without the table that raises the exception.
2) We dont use RAID.
Thank you
On Wed, Apr 19, 2017 at 12:49 PM, Vick Khera wrote:
> 1) restore from backup
> 2) fix whatever configuration you made to
Il 19/04/2017 17:49, Vick Khera ha
scritto:
1) restore from backup
2) fix whatever configuration you made to let windows (or
your hardware) destroy your data on crash. is there some RAID
cache that is not backed up by a battery?
1) restore from backup
2) fix whatever configuration you made to let windows (or your hardware)
destroy your data on crash. is there some RAID cache that is not backed up
by a battery?
On Wed, Apr 19, 2017 at 10:18 AM, Alexandre wrote:
> Hello,
>
> The computer had a
Hello,
The computer had a unexpected shutdown, it is a Windows machine.
Now some data appears to be corrupted, I am receiving exceptions like this:
ERROR: could not read block 0 in file "base/16393/16485": read only
0 of 8192 bytes
There is some way to correct this?