From: Tom Lane <tgl@sss.pgh.pa.us>
To: mattwelchwork@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16955: Replication port problems
Date: Thu, 08 Apr 2021 11:15:34 -0400
Message-ID: <1847748.1617894934@sss.pgh.pa.us> (raw)
In-Reply-To: <16955-354a52705465f672@postgresql.org>
References: <16955-354a52705465f672@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Given that port 5123 is operative on the primary rather than the secondary,
> why should SELinux on the secondary be recording issues for port 5123 ?
This hardly seems like a bug. The entire *point* of SELinux is to prevent
daemon processes from doing unexpected things like connecting to ports
that they shouldn't.
> Issue is resolved by running "semanage port -a -t postgresql_port_t -p tcp
> 5123" on the secondary
And that's where you told SELinux it was okay. But I would not expect
the out-of-the-box configuration to allow this, and it didn't.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, mattwelchwork@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16955: Replication port problems
In-Reply-To: <1847748.1617894934@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox