Re: query against pg_locks leads to large memory alloc

Поиск
Список
Период
Сортировка
От Dave Owens
Тема Re: query against pg_locks leads to large memory alloc
Дата
Msg-id CA+OQrzjSJTaUMs5y5Ar=_aipSa115d7qNSZy==w8MiDEdG27Uw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: query against pg_locks leads to large memory alloc  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: query against pg_locks leads to large memory alloc
Список pgsql-performance
Hi Andres,

On Tue, Aug 19, 2014 at 10:17 AM, Andres Freund <andres@2ndquadrant.com> wrote:
>> max_connections = 450 ...we have found that we run out of shared
>> memory when max_pred_locks_per_transaction is less than 30k.
>
> What was the precise error message when that happened?

2014-07-31 15:00:25 PDT 53dabbea.29c7ERROR:  53200: out of shared memory
2014-07-31 15:00:25 PDT 53dabbea.29c7HINT:  You might need to increase
max_pred_locks_per_transaction.
2014-07-31 15:00:25 PDT 53dabbea.29c7LOCATION:  CreatePredicateLock,
predicate.c:2247
2014-07-31 15:00:25 PDT 53dabbea.29c7STATEMENT:  SELECT member_id,
SUM(credit_quarters) FROM ondeck_tallies_x WHERE team_id = $1 AND
credit_quarters > 0 AND EXTRACT(day from current_timestamp -
dt_attendance_taken) <= $2 GROUP BY member_id


В списке pgsql-performance по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc
Следующее
От: Dave Owens
Дата:
Сообщение: Re: query against pg_locks leads to large memory alloc