BUG #16151: startup timing problem

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: phjvdmeij(at)gmail(dot)com
Subject: BUG #16151: startup timing problem
Date: 2019-12-05 10:39:25
Message-ID: 16151-40246ef87d3001eb@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16151
Logged by: paul van der meij
Email address: phjvdmeij(at)gmail(dot)com
PostgreSQL version: 12.1
Operating system: fedora 31
Description:

after startup of fedora, communication with postgresql from a client is not
working.
a 'systemctl stop postgresql' en 'systemctl start postgresql' solves the
problem

in the startup script /usr/lib/systemd/system/postgresql.service:
'network.target' should be 'network-online.target'

this solves the problem

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message RideNext 2019-12-05 10:50:54 RE: Postgres takes more than 6 minutes to come up during host/standby switch over
Previous Message PG Bug reporting form 2019-12-05 09:17:34 BUG #16150: UPDATE set NULL value in non-null columns