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

The following bug has been logged on the website:

Bug reference: 14098
Logged by: John Lumby
Email address: johnlumby(at)hotmail(dot)com
PostgreSQL version: 9.5.2
Operating system: linux 64-bit
Description:

If postgresql exhausts the space reserved for locks, whose size is defined
by
max_locks_per_transaction * (max_connections + max_prepared_transactions)
locks,
then it issues this message :

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

The words "out of shared memory" are misleading (and ungrammatical, and
somewhat contradict the HINT).
Shared mem space is not exhausted, lock table space is exhausted.

Please change the message to

psql: FATAL: lock table space is exhausted
HINT: You might need to increase max_locks_per_transaction.

I believe all cases of this msg are in
src/backend/storage/lmgr/lock.c