gargoyle creates too long socket filenames

[danbornside]

when running gargoyle in long pathnames, launching postgres fails because the filename of the unix domain socket is too long (max 107 on linux)

postgres (PostgreSQL) 9.5.9
[dbornside@bornside tezos-bake-central]$ "/nix/store/phf8zhbbvfar40fz3jdbfxq9bg5l6hvp-postgresql-9.5.9/bin/postgres" "-h" "" "-D" "/home/dbornside/src/obsidian/tezos-baking-platform/tezos-bake-monitor/tezos-bake-central/place/bake-monitor/db/work" "-k" "/home/dbornside/src/obsidian/tezos-baking-platform/tezos-bake-monitor/tezos-bake-central/place/bake-monitor/db/work"
LOG:  Unix-domain socket path "/home/dbornside/src/obsidian/tezos-baking-platform/tezos-bake-monitor/tezos-bake-central/place/bake-monitor/db/work/.s.PGSQL.5432" is too long (maximum 107 bytes)
WARNING:  could not create Unix-domain socket in directory "/home/dbornside/src/obsidian/tezos-baking-platform/tezos-bake-monitor/tezos-bake-central/place/bake-monitor/db/work"
FATAL:  could not create any Unix-domain sockets
[dbornside@bornside tezos-bake-central]$

I think tmp-postgres is the furthest along in dealing with boundary conditions like this. The author studied pg_tmp before writing his utility and it uses a temporary directory instead to create the socket file within.