fix panic with generic error

[diogob]

This refers to #20

• When PQ.socket fails we just need to wait, the connection should be starting or resetting
• Panic and try to get libpq message when consumeInput fails
• Reformat

[steve-chavez]

Thanks a lot for the quick fix @diogob.

I'm already seeing a more informative error message with this change:

12/Mar/2024:17:41:57 -0500: FatalError {fatalErrorMessage = "\"server closed the connection unexpectedly\\n\\tThis probably means the server terminated abnormally\\n\\tbefore or while pro
cessing the request.\\n\""}. Retrying listening for notifications on the pgrst channel..

This when terminating the pg connection manually with:

select pg_terminate_backend(pid) from pg_stat_activity where application_name ilike '%postgrest%' and query ilike '%listen%';

---

Would it be possible to unwrap the error message? Perhaps by exporting FatalError? No problem if not. Otherwise the PR looks good to me 👍

[diogob]

@steve-chavez could you test again? I have exported FatalError for testing but also have added a new show instance that should give you a neater interface to the error message.

[steve-chavez]

@diogob Looks great!

13/Mar/2024:09:59:25 -0500: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

Also, exporting FatalError is no longer necessary now that there's instance Show FatalError 👍