> The name max_locks_per_transaction indicates a limit of some kind. The
> documentation doesn't mention anything about whether that limit is
> or not.
> I suggest the additional wording:
> "This parameter is not a hard limit: No limit is enforced on the
> locks in each transaction. System-wide, the total number of locks is
> by the size of the lock table."
I think it's worse than that. First of all, user locks persist outside
of transactions, but they apply to this limit. A more appropriate name
for the GUC variable would be 'estimated_lock_table_size_per_backend',
or something like that. I've been putting some thought into reworking
the userlock contrib module into something acceptable into the main
project, a substantial part of that being documentation changes.
pgsql-hackers by date
|Next:||From: Merlin Moncure||Date: 2004-09-30 13:45:51|
|Subject: spurious function execution in prepared statements.|
|Previous:||From: John DeSoi||Date: 2004-09-30 12:00:45|
|Subject: looking for pgEdit beta testers|