https://github.com/postgres/postgres/blob/master/src/backend... :

> Therefore, they offer both exclusive and shared lock modes (to support read/write and read-only access to a shared object). There are few other frammishes. User-level locking should be done with the full lock manager --- which depends on LWLocks to protect its shared state.

It sort of makes sense in context, as a "feature" or a "flourish". It also appears on the pg_hackers mailing list:

> There has been some talk of separating the power to create new users from the power of being superuser (although presumably only a superuser should be allowed to create new superusers). If the planned pg_role rewrite gets submitted before the 8.1 feature freeze, I might look at adding that frammish into it.

and here, from 19 years ago:

> And we get ragged on regularly for the non-SQL-standard features we've inherited from Berkeley Postgres (eg, the implicit-FROM frammish that was under discussion yesterday).

No amount of googling turns up a formal definition or usage outside of the Postgres community. "frammish.org" doesn't seem to be related.

Are Postgres developers starting to evolve their own dialect? Should we call an anthropologist?