Kevin Grittner writes:
> Dave Owens wrote:
>> max_connections = 450 ...we have found that we run out of shared
>> memory when max_pred_locks_per_transaction is less than 30k.
> It gathers the information in memory to return for all those locks
> (I think both the normal heavyweight locks and the
Dave Owens wrote:
> max_connections = 450 ...we have found that we run out of shared
> memory when max_pred_locks_per_transaction is less than 30k.
>> SELECT COUNT(*) from pg_locks;
>
> ERROR: invalid memory alloc request size 1562436816
It gathers the information in memory to return for all
On Mon, Aug 18, 2014 at 2:21 PM, Matheus de Oliveira
wrote:
> Do you really need such large values? What is your max_connections value?
max_connections = 450 ...we have found that we run out of shared
memory when max_pred_locks_per_transaction is less than 30k.
On Mon, Aug 18, 2014 at 2:29 PM, M
On Mon, Aug 18, 2014 at 4:21 PM, Matheus de Oliveira
wrote:
>
> On Mon, Aug 18, 2014 at 6:01 PM, Dave Owens wrote:
>>
>> max_locks_per_transaction = 9000
>> max_pred_locks_per_transaction = 4
performance of any query to pg_locks is proportional to the setting of
max_locks_per_transaction. s
On Mon, Aug 18, 2014 at 6:01 PM, Dave Owens wrote:
> max_locks_per_transaction = 9000
> max_pred_locks_per_transaction = 4
>
Do you really need such large values? What is your max_connections value?
Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível
Hi,
I have a tool that is trying to collect stats from postgres (v9.1.13).
postgres attempts to allocate more memory than is allowed:
SELECT mode, count(mode) AS count FROM pg_locks GROUP BY mode ORDER BY mode;
ERROR: invalid memory alloc request size 1459291560
Memory-related configs from the
