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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gurjeet Singh <gurjeet(at)singh(dot)im>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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-09-07 19:33:57
Message-ID: ZPolpbGJR/aDfxJu@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 12, 2023 at 11:57:45PM -0700, Gurjeet Singh wrote:
> On Mon, Jun 12, 2023 at 10:59 PM Nathan Bossart
> <nathandbossart(at)gmail(dot)com> wrote:
> > On Sat, May 27, 2023 at 03:17:21PM -0700, Gurjeet Singh wrote:
> > > If listen_addresses is empty, then server won't try to open any TCP/IP
> > > ports. The patch does not change any language related to that.
> >
> > Your proposed change notes that the server only starts if it can listen on
> > at least one TCP/IP address, which I worry might lead folks to think that
> > the server won't start if listen_addresses is empty.
>
> Perhaps we can prefix that statement with "If listen_addresses is not
> empty", like so:

I came up with a slightly modified doc patch, attached.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

Attachment Content-Type Size
listen.diff text/x-diff 1009 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gabriele Bartolini 2023-09-07 19:51:14 Possibility to disable `ALTER SYSTEM`
Previous Message Robert Haas 2023-09-07 19:29:48 Re: Eliminate redundant tuple visibility check in vacuum