Re: How to crash postgres using savepoints

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: How to crash postgres using savepoints
Date: 2006-11-16 20:59:17
Message-ID: 455CD125.2060309@selectacast.net
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugspgsql-general

Tom Lane wrote:
> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
>> See example below. At the very least the documentation needs to tell
>> users that savepoints use shared memory, and the cofusing HINT string
>> needs to be changed to something more useful.
>
> Which part of "You may need to increase max_locks_per_transaction" do
> you find confusing? If you actually need tens of thousands of nested
> savepoints then this is accurate advice.

Because there is nothing anywhere that indicates that a savepoint uses a
lock. When I got the message the first time I was very confused and had
nowhere to look to figure out what the real problem was. A more helpful
message would be "You may need to increase max_locks_per_transaction, or
release your savepoints more often"

Why does a savepoint need shared memory anyway, if it is only useful
inside the transaction it was created in?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2006-11-16 20:59:33 Re: How to crash postgres using savepoints
Previous Message Tom Lane 2006-11-16 20:35:11 Re: How to crash postgres using savepoints

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2006-11-16 20:59:33 Re: How to crash postgres using savepoints
Previous Message Martijn van Oosterhout 2006-11-16 20:56:46 Re: Linux hard drive/device nodes for a Postgres RAID array