From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Don Seiler <don(at)seiler(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: ERROR: invalid memory alloc in Pg 9.6.6 |
Date: | 2018-04-13 16:09:22 |
Message-ID: | 20180413160921.GO27724@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Greetings,
* Don Seiler (don(at)seiler(dot)us) wrote:
> Started seeing "invalid memory alloc" errors in a non-production DB (9.6.6)
> all of a sudden this afternoon. It's running on CentOS 7.4 on VMWare.
>
> I ran a pg_dump on that DB and got this error almost immediately:
>
> pg_dump: [archiver (db)] query failed: ERROR: invalid memory alloc request
> size 8830452760576
That's interesting. An invalid memory alloc request size complaint such
as that tends to be an indicator of corruption or a bug in the backend
possibly.
Certainly curious that you were able to run the query and not hit that..
Are you sure you were running it exactly the way pg_dump does? There's
a bunch of setup that pg_dump does early on, maybe log all queries when
you run the pg_dump and then in a psql session try running them..?
If you can reliably reproduce this with either pg_dump or psql, then the
next step would perhaps be jumping in with gdb to see where that error
is being hit..
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Don Seiler | 2018-04-13 16:13:20 | Re: ERROR: invalid memory alloc in Pg 9.6.6 |
Previous Message | Jaime Soler | 2018-04-13 08:51:20 | Re: ERROR: invalid memory alloc in Pg 9.6.6 |