| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> | 
|---|---|
| To: | Vidhya Bondre <meetvbondre(at)gmail(dot)com> | 
| Cc: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: Out of shared memory in postgres 8.4.2 and locks | 
| Date: | 2010-03-09 12:34:11 | 
| Message-ID: | b42b73151003090434yabba5me4489096769d4bc7@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-performance | 
On Tue, Mar 9, 2010 at 4:38 AM, Vidhya Bondre <meetvbondre(at)gmail(dot)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?
In any event, increase the max_locks_per_transaction setting and
restart the database.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-03-09 12:46:27 | Re: Extracting superlatives - SQL design philosophy | 
| Previous Message | Vidhya Bondre | 2010-03-09 09:38:53 | Out of shared memory in postgres 8.4.2 and locks |