Relax validation on the postgres service address setting

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?

[tankyleo]

Relax validation on the postgres service address setting
We previously parsed the postgres service address setting into a
`std::net::SocketAddr`, which was overly restrictive, and
prevented the use of hostnames for that setting.
The postgres service address is logged on startup, so the user can check
that the service address is correctly configured in case of a failure
to connect to the postgres database on startup.

[ldk-reviews-bot]

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

[tnull]

In #73 we made the same change for bind_address. We should probably revert that, too, no?