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

From Euler Taveira
Subject Re: invalid memory alloc request size from pg_stat_activity?
Date
Msg-id CAHE3wghviO-OZK5=ZQ8YwXaq50xcVyCUARDCyaTk1viKiY=Qhw@mail.gmail.com
Whole thread Raw
In response to invalid memory alloc request size from pg_stat_activity?  (James Tomson <james@pushd.com>)
Responses Re: invalid memory alloc request size from pg_stat_activity?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
Em seg, 6 de mai de 2019 às 20:04, James Tomson <james@pushd.com> escreveu:
>
> 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 is because it is limited to 1GB - 1.

> Maybe this has to do with us setting track_activity_query_size=102400? Is there a known safe maximum for that, or
couldthere be some other problem? 
>
Question is: why do you want to return such a big query text? That's
impractical for admin/monitoring tools. We can usually identify a
query with 1024 bytes (that is the default).


--
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento



pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #15793: Required Community Version Installs not thecustomized EnterpriseDB one.
Next
From: Stephen Frost
Date:
Subject: Re: BUG #15793: Required Community Version Installs not thecustomized EnterpriseDB one.