ERROR: out of shared memory - But the table is empty

From: Stefan Schwarzer <stefan(dot)schwarzer(at)unep(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: ERROR: out of shared memory - But the table is empty
Date: 2012-07-12 14:53:36
Message-ID: 110F67E5-6A23-48E4-9CB8-F05D0CC79E8D@unep.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi there,

not being an expert for Postgres…. I have a Postgis table with the countries of the world. Now, I would like to drop it. I got the error message:

ERROR: out of shared memory
HINT: You might need to increase max_locks_per_transaction.

and thought that it would be easier to drop first all rows, and then drop the empty table.

But it seems that it has a problem with dropping the index:

DROP INDEX gis.countries_uid;

actually generates that error message.

So, do I need to dig now into the postgres config file? It seems strange to me that Postgres has a problem deleting an empty table, though.

Thanks for any hints.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Sabino Mullane 2012-07-12 16:59:17 Re: Bug? Prepared queries continue to use search_path from their preparation time
Previous Message David Johnston 2012-07-12 14:22:37 Re: PostgreSQL limitations question