Re: invalid memory alloc request size from pg_stat_activity?

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: James Tomson <james(at)pushd(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Eric Jensen <ej(at)pushd(dot)com>
Subject: Re: invalid memory alloc request size from pg_stat_activity?
Date: 2019-05-07 13:37:41
Message-ID: CAHE3wghviO-OZK5=ZQ8YwXaq50xcVyCUARDCyaTk1viKiY=Qhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Em seg, 6 de mai de 2019 às 20:04, James Tomson <james(at)pushd(dot)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 could there 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Frost 2019-05-07 14:44:46 Re: BUG #15793: Required Community Version Installs not the customized EnterpriseDB one.
Previous Message Magnus Hagander 2019-05-07 10:12:27 Re: BUG #15793: Required Community Version Installs not the customized EnterpriseDB one.