| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Fletcher <markf(at)corp(dot)groups(dot)io> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Shared buffer hash table corrupted |
| Date: | 2020-02-22 17:34:40 |
| Message-ID: | 28090.1582392880@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mark Fletcher <markf(at)corp(dot)groups(dot)io> writes:
> Thanks for the response. I did restart the postmaster yesterday. Earlier
> this morning, a query that normally completes fine started to error out
> with 'invalid memory alloc request size 18446744073709551613'. Needless to
> say our database isn't quite that size. This query was against a table in a
> different database than the one that had the corruption warning yesterday.
> Restarting the postmaster again fixed the problem. For good measure I
> restarted the machine as well.
Um. At that point I'd agree with your concern about developing hardware
problems. Both of these symptoms could be easily explained by dropped
bits in PG's shared memory area. Do you happen to know if the server
has ECC RAM?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Fletcher | 2020-02-22 17:44:12 | Re: Shared buffer hash table corrupted |
| Previous Message | Adrian Klaver | 2020-02-22 17:33:37 | Re: Replication: slave server has 3x size of production server? |