After a connection reset, psql should re-read the connection variables. This was was initially reported by ysch on IRC and confirmed in the code by Zr40. All I'm doing here is making sure that it is reported, as per ysch's request.
I quickly verified this as following:
1. start 11 instance
2. psql into it
3. stop 11 instance
4. start 10 instance
5. in the existing psql session, first trigger a reconnect ('select 1') and then '\df', which depends on the server version. I got:
ERROR: column p.prokind does not exist LINE 5: CASE p.prokind
This happens because the psql session believes it is still connected to the 11 instance, as confirmed by Zr40:
