You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#336 adds the new log details when waiting on pg_isready, earlier than mentioned above. Putting the output here gives the user time to cancel the run. Putting the log later doesn't give the user any time to react.
External connection example with the lines before and after.
2023-06-02 19:48:01,536:INFO:pgosm-flex:db:Checking for Postgres service to be available
2023-06-02 19:48:01,536:INFO:pgosm-flex:db:Connecting to Postgres using role "pgosm_flex" on host "172.16.0.170:5432" in database "pgosm_dev"
2023-06-02 19:48:07,668:INFO:pgosm-flex:db:Postgres instance ready
Internal example (only the new line)
2023-06-02 19:56:43,147:INFO:pgosm-flex:db:Connecting to Postgres using role "postgres" on host "localhost:5432" in database "pgosm"
Details
Now that I'm using
--force
in development, I'd really a reassurance that I'm really waiting on a Dev connection and not accidentally a prod one.This line explains it's an external connection (only time I really care):
Maybe extend the line with
The text was updated successfully, but these errors were encountered: