Re: Re: BUG #14098: misleading message "out of shared memory" when lock table space exhausted

On Tue, 19 Apr 2016 13:36:35 -0400
John Lumby <johnlumby(at)hotmail(dot)com> wrote:

> I now see that as you've explained,  the words     
>             out of shared memory
> are not wrong.   However,   I think it may be more helpful to change them to          
>            lock table space is exhausted
> as I previously suggested.
> The reason being that ,  for most people,  intuitively,  telling them
>     " out of shared memory "
> would indicate to try to *reduce* the consumption of this resource,
> whereas the hint tells them  to *increase* something.
> I think there is a clearer connection between insufficient lock table space
> and increasing max_locks_per_transaction.

There are reasons besides locks that can lead to consuming all the allocated
shared memory. A message that specifically blamed locks would actively mislead
a user who was trying to diagnose one of the less common cases.

-dg

--
David Gould daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.