n on y (cost=0.00..12.80 rows=280 width=76)
-> Index Scan using x_pkey on x (cost=0.14..0.18 rows=1 width=40)
Index Cond: (a = temp_table.a)
Thanks,
Stefan
On 31/01/2018 21:23, Tomas Vondra wrote:
On 01/31/2018 09:51 PM, Jan Wieck wrote:
On Wed, Jan 31, 201
back with a number when we next
hit the "invalid memory alloc".
Stefan
On 11/03/2020 15:37, Tom Lane wrote:
Stefan Blanke writes:
We've upgraded to PostgreSQL 11.5 (postgresql.org rhel 6 rpm) and I have
had another occurrence of this invalid alloc of 1GB. Apologies for never
p
Hello,
We've tripped over an error when doing a "COPY.. TO STDOUT WITH BINARY"
query.
"ERROR: invalid memory alloc request size 1073741824"
(exactly 1GB)
So a palloc() call is failing on the AllocSizeIsValid() check.
Does anyone know if this a safety catch we are tripping with a bad query
n a corrupted TOAST entry. Is this happening on
>> trustworthy hardware or beige box with no ECC or RAID?
It's good quality commercial hardware in our colo - no exactly sure what.
Thanks for taking the time to look at this!
Stefan
On 01/30/18 22:00, Tomas Vondra wrote:
On 01/
