Igor Artemenko 88fe0d6411 Simplify pg_isready usage ...

The pg_isready documentation says that it does not need a correct
database name or username to get the server status. In fact, incorrect
values result in the server logging failed connection attempts. As a
result, when we set DB_NAME to ALL, calls to the check_availability
function (which uses pg_isready) cause the server to log the following
error:

    FATAL:  database "ALL" does not exist

To eliminate this error, this change simplifies the pg_isready call.

2023-03-20 22:51:05 +00:00

..

assets

Simplify pg_isready usage

2023-03-20 22:51:05 +00:00

etc

Remove url [en|de]code functions

2022-10-10 11:53:09 -07:00

usr/local/bin

Fix postgres restore wrong db type

2022-07-22 09:41:55 +07:00