Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)

От: Kevin Grittner
Тема: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)
Дата: ,
Msg-id: 4C2477A20200002500032B03@gw.wicourts.gov
(см: обсуждение, исходный текст)
Ответ на: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah)
Ответы: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah)
Список: pgsql-performance

Скрыть дерево обсуждения

sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
 Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Devrim GÜNDÜZ, )
 Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Yeb Havinga, )
  Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
   Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  ("Kevin Grittner", )
    Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
     Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
      Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Tom Molesworth, )
       Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
        Re: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Tom Molesworth, )
      Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  ("Kevin Grittner", )
       Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
        Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )
      Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Greg Smith, )
       Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)  (Rajesh Kumar Mallah, )

Rajesh Kumar Mallah <> wrote:

> its now non business hours and
> SELECT procpid,current_query   from pg_stat_activity where
> current_query not ilike '%idle%' ;
> is just 5-10, i am yet to measure it during business hours.

Be careful about '<IDLE> in transaction' status.  Those are a
problem if the transaction remains active for very long, because
vacuum (autovacuum or otherwise) can't free space for dead rows
which could still be visible to the '<IDLE> in transaction'
connection.  It's normal to see this status briefly between
statements in a transaction, but it's a problem if a connection just
sits there in this status.

-Kevin


В списке pgsql-performance по дате сообщения:

От: tony@exquisiteimages.com
Дата:
Сообщение: Architecting a database
От: Tom Molesworth
Дата:
Сообщение: Re: Re: sudden spurt in swap utilization (was:cpu bound postgresql setup.)