From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Souquieres Adam <adam(dot)souquieres(at)axege(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |
Date: | 2014-05-12 13:21:03 |
Message-ID: | CAHyXU0xEuMxrTOB9PtBGhw=n3kMeTN4U39we0LVqaRqHeX9rpA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 12, 2014 at 7:57 AM, Souquieres Adam
<adam(dot)souquieres(at)axege(dot)com> wrote:
> Hi,
>
> we have a problem since we migrate from 8.4 to 9.1
>
> when we play : ANALYSE VERBOSE; ( stat on all databases, with 500 tables and
> 1to DATA in all tables)
>
> we now have this message :
>
> org.postgresql.util.PSQLException: ERROR: out of shared memory Indice : You
> might need to increase max_locks_per_transaction.
>
> When we was in 8.4, there was no error,
>
> there is our specific postgresql.conf configuration on the server :
>
> default_statistics_target = 200
> maintenance_work_mem = 1GB
> constraint_exclusion = on
> checkpoint_completion_target = 0.9
> effective_cache_size = 7GB
> work_mem = 48MB
> wal_buffers = 32MB
> checkpoint_segments = 64
> shared_buffers = 2304MB
> max_connections = 150
> random_page_cost = 2.0
> max_locks_per_transaction = 128 # was at default val ( 64?), we already try
> to increase it without sucess
How high did you increase it? It's not uncommon to have to raise that
parameter significantly if you have a lot of tables. Try 2048.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-05-12 13:29:10 | Re: 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |
Previous Message | Souquieres Adam | 2014-05-12 12:57:15 | 8.4 -> 9.1 : ANALYSE VERBOSE; -> out of shared memory |