Re: shared memory/max_locks_per_transaction error

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Kynn Jones <kynnjo(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: shared memory/max_locks_per_transaction error
Date: 2008-03-17 15:00:05
Message-ID: 20080317150005.GF4317@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kynn Jones escribió:

> I'm leaning towards the re-design option, primarily because I really don't
> really understand the consequences of cranking up max_locks_per_transaction.
> E.g. Why is its default value 2^6, instead of, say, 2^15?

It's because it (partly) defines how much shared memory the server will
use.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sathiya psql 2008-03-17 15:18:14 postgresql performance tuning tools
Previous Message Gauthier, Dave 2008-03-17 14:58:44 Catch-22