From: Vidhya Bondre <meetvbondre@gmail.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Out of shared memory in postgres 8.4.2 and locks
Date: Tue, 9 Mar 2010 18:57:17 +0530
Message-ID: <919b7db61003090527k3c8ad4cw84b70e55bd15cd1e@mail.gmail.com> (raw)
In-Reply-To: <b42b73151003090434yabba5me4489096769d4bc7@mail.gmail.com>
References: <919b7db61003090138j6da56dffu5e0ddd4276168b48@mail.gmail.com>
<b42b73151003090434yabba5me4489096769d4bc7@mail.gmail.com>
On Tue, Mar 9, 2010 at 6:04 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
> On Tue, Mar 9, 2010 at 4:38 AM, Vidhya Bondre <meetvbondre@gmail.com>
> wrote:
> > Hi All,
> >
> > We have installed postgres 8.4.2 on production.
> >
> > We have a parition table structure for one of the table.
> >
> > when i am drop the master table we get the following error.
> >
> > drop table table_name cascade;
> > WARNING: out of shared memory
> > ERROR: out of shared memory
> > HINT: You might need to increase max_locks_per_transaction.
> >
> > FYI : This sql was working fine on Postgres 8.3
> >
> > Can some one please let me know what is going wrong here.
>
> are you using the same postgresql.conf? have you created more
> partitions? using advisory locks?
>
Yes we are using same conf files. In a week we create around 5 partitions.
We are not using advisory locks
>
> In any event, increase the max_locks_per_transaction setting and
> restart the database.
>
Currently the value of max_locks_per_transaction is 64 modifying it to 96
works.
Have a couple of questions
1] As and when we add partitions will we have to increase this parameter ?
2] will we have to consider any othe parameter twick while increasing this
one?
>
> merlin
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: meetvbondre@gmail.com, mmoncure@gmail.com
Subject: Re: Out of shared memory in postgres 8.4.2 and locks
In-Reply-To: <919b7db61003090527k3c8ad4cw84b70e55bd15cd1e@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox