On Sat, Feb 22, 2020 at 9:34 AM Tom Lane wrote:
>
> 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?
>
> Yes, it
Mark Fletcher 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 que
On Fri, Feb 21, 2020 at 2:53 PM Tom Lane wrote:
>
> Personally, I'd restart the postmaster, but not do more than that unless
> the error recurs.
>
Thanks for the response. I did restart the postmaster yesterday. Earlier
this morning, a query that normally completes fine started to error out
with
Mark Fletcher writes:
> Running 9.6.15, this morning we got a 'shared buffer hash table corrupted'
> error on a query. I reran the query a couple hours later, and it completed
> without error. This is running in production on a Linode instance which
> hasn't seen a
Hi All,
Running 9.6.15, this morning we got a 'shared buffer hash table corrupted'
error on a query. I reran the query a couple hours later, and it completed
without error. This is running in production on a Linode instance which
hasn't seen any config changes in months.
I didn
