From: Tom Lane <tgl@sss.pgh.pa.us>
To: tdryden@comcast.net
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: PostgreSQL 15 on Fedora 37 Does not start after reboot
In-reply-to: <e6d2c602-db46-0709-6519-ade189fa5203@comcast.net>
References: <e6d2c602-db46-0709-6519-ade189fa5203@comcast.net>
Comments: In-reply-to Tom Dryden <tdryden@comcast.net>
	message dated "Sun, 01 Jan 2023 17:55:07 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1309909.1672614883.1@sss.pgh.pa.us>
Date: Sun, 01 Jan 2023 18:14:43 -0500
Message-ID: <1309910.1672614883@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1309910.1672614883%40sss.pgh.pa.us>
Precedence: bulk

Tom Dryden <tdryden@comcast.net> writes:
> PostgreSQL 15 on Fedora 37 Does not start after reboot
> The service is enabled and reports a network error after reboot. 
> Starting the postgresql service manually after the reboot is successful.

>  From the log file:

> 2023-01-01 09:22:26.406 EST [812] LOG: starting PostgreSQL 15.1 on 
> x86_64-pc-linux-gnu, compiled by gcc (GCC) 12.2.1 20220819 (Red Hat 
> 12.2.1-2), 64-bit
> 2023-01-01 09:22:26.406 EST [812] LOG: could not bind IPv4 address 
> "192.168.122.124": Cannot assign requested address

This indicates that Postgres is starting before the network
interface is up, something that systemd is prone to try to do.

> Suggested fix:
> Edit /usr/lib/systemd/system/postgresql-15.service and change the
> After=network.target line to
> After=network-online.target

Right, although some authorities suggest also adding
Wants=network-online.target

In any case, that service file is not created or distributed by us.
I suggest filing this as a bug against the Fedora postgresql package.

			regards, tom lane