Re: invalid memory alloc request size from pg_stat_activity? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: invalid memory alloc request size from pg_stat_activity?
Date
Msg-id 28356.1557241170@sss.pgh.pa.us
Whole thread Raw
In response to invalid memory alloc request size from pg_stat_activity?  (James Tomson <james@pushd.com>)
List pgsql-bugs
James Tomson <james@pushd.com> writes:
> We're upgrading from postgresql 9.6 to 10.6 and everything is working fine, but any query against pg_stat_activity
resultsin ERROR:  invalid memory alloc request size 1652113408 

> e.g:

> ourdb=> SELECT pid, state, age(query_start, clock_timestamp()), usename, query FROM pg_stat_activity WHERE query !=
'<IDLE>'AND state != 'idle' ORDER BY age limit 100; 
> ERROR:  invalid memory alloc request size 1652113408

That seems odd ...

> Maybe this has to do with us setting track_activity_query_size=102400?

It wouldn't surprise me if reading pg_stat_activity causes allocation of
track_activity_query_size * max_connections bytes, but unless you also
have max_connections set to some pretty insane value, that wouldn't
be enough to fit this observation.

Did you have these parameters set differently in 9.6?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: invalid memory alloc request size from pg_stat_activity?
Next
From: Tom Lane
Date:
Subject: Re: invalid memory alloc request size from pg_stat_activity?