Re: Document that server will start even if it's unable to open some TCP/IP ports

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Gurjeet Singh <gurjeet(at)singh(dot)im>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Document that server will start even if it's unable to open some TCP/IP ports
Date: 2023-06-13 20:28:31
Message-ID: 1800867.1686688111@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> Before we spend too much time trying to document the current behavior, I
> think we should see if we can change it to something less surprising (i.e.,
> failing to start if the server fails for any address). The original
> objections around kernel support for IPv6 might no longer stand.

I think that'd be more surprising not less.

The systemd guys certainly believe that daemons ought to auto-adapt
to changes in the machine's internet connectivity. We aren't there
yet, but I can imagine somebody trying to fix that someday soon.
If the postmaster is able to dynamically acquire and drop ports then
it would certainly not make sense to behave as you suggest.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2023-06-13 20:47:08 Re: Meson build updates
Previous Message Joel Jacobson 2023-06-13 20:23:57 Re: Do we want a hashset type?