| From: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Invalid field size |
| Date: | 2017-07-04 16:07:30 |
| Message-ID: | 5d1eeda2-a37a-809e-dc12-28fd404a6149@evolu-s.it |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Il 04/07/2017 17:42, Daniel Verite ha scritto:
> Moreno Andreo wrote:
>
>> As you can see I have 2 bytea fields, blob and thumbnail (the one it
>> seems it's giving the error), but AFAIK the former is never used, so it
>> should be always null.
>> Googling around did not help.
>
> Despite the auto-correction mechanisms in place in modern drives [1],
> the probability of a non-correctable error is not negligible,
> so it's plausible that it's what you're experiencing.
>
> If that's the case and only byte is wrong in the whole file, you could
> theorically fix it by finding the offset of the offending length and patch
> the wrong byte with a 0xff value.
>
>
> [1]
> https://en.wikipedia.org/wiki/Hard_disk_drive#Error_rates_and_handling
>
So if it's the case (hardware error), recalling a new backup should
reproduce the error, right?
When the user comes back from holidays I'll call him and check this.
Thanks
Moreno.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-07-04 16:15:16 | Re: Invalid field size |
| Previous Message | Moreno Andreo | 2017-07-04 16:03:36 | Re: [SPAM] Re: Invalid field size |