| From: | Dave Owens <dave(at)teamunify(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: query against pg_locks leads to large memory alloc |
| Date: | 2014-08-19 17:25:50 |
| Message-ID: | CA+OQrzjSJTaUMs5y5Ar=_aipSa115d7qNSZy==w8MiDEdG27Uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi Andres,
On Tue, Aug 19, 2014 at 10:17 AM, Andres Freund <andres(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Owens | 2014-08-19 17:50:41 | Re: query against pg_locks leads to large memory alloc |
| Previous Message | Andres Freund | 2014-08-19 17:17:10 | Re: query against pg_locks leads to large memory alloc |