Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uyfI2-00B5gr-OX for pgsql-admin@arkaria.postgresql.org; Tue, 16 Sep 2025 23:40:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uyfHz-003FC3-2G for pgsql-admin@arkaria.postgresql.org; Tue, 16 Sep 2025 23:40:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uyfHy-003FBu-1R for pgsql-admin@lists.postgresql.org; Tue, 16 Sep 2025 23:40:47 +0000 Received: from m16.mail.126.com ([220.197.31.7]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uyfHr-000nye-3A for pgsql-admin@postgresql.org; Tue, 16 Sep 2025 23:40:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=Content-Type:From:Mime-Version:Subject:Date: Message-Id:To; bh=FSiSJ8+1le06IAuGvVy7lGsy307JdagD6/poApRFDjc=; b=WnLO70U2+G+9ifRzt38d+1XJtWYzXek08i1PWsssyHqC00bABwF8O+zK+nWqYD 2B2RrOLfucUNtGKsduK3W7LEOe5zFRL9n9IZcFkO1PC0umkX55NbAYtAU2IBivD2 YxKpDcAzEB4DSCxvgZ6JgCydXeFVFrE1FxutBHNAKbdl0= Received: from smtpclient.apple (unknown []) by gzga-smtp-mtada-g1-1 (Coremail) with SMTP id _____wDnV9pu9clojQtjAw--.43916S2; Wed, 17 Sep 2025 07:40:30 +0800 (CST) Content-Type: multipart/alternative; boundary=Apple-Mail-576B0BCC-B7A1-41C6-826D-D9B3B7FEDD0D Content-Transfer-Encoding: 7bit From: =?utf-8?B?5p2O5piO?= Mime-Version: 1.0 (1.0) Subject: Re: Allow connections by IP address? Date: Wed, 17 Sep 2025 07:40:17 +0800 Message-Id: <2DFE4EC0-7374-4D5E-BC05-49530F7015A0@126.com> References: Cc: pgsql-admin In-Reply-To: To: Ron Johnson X-Mailer: iPhone Mail (20D67) X-CM-TRANSID: _____wDnV9pu9clojQtjAw--.43916S2 X-Coremail-Antispam: 1Uf129KBjvdXoWrtr48AFyDtryrJF4rWrykKrg_yoWfWFX_ua 4vka97WwsrGr48u3y3Krnakr97AFWUCw1xt3y3XF1IgFyY93WSqrs7Ww1av3W3Zrnaywnx G3WrZ34Y93ZavjkaLaAFLSUrUUUUjb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7sR_6pB3UUUUU== X-Originating-IP: [2408:8418:30:25d4:39b5:c95d:3050:eeb7] X-CM-SenderInfo: polpx0jjrykjirw6ij2wof0z/1tbi3BvKa2jJ5nCVPQAAs5 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail-576B0BCC-B7A1-41C6-826D-D9B3B7FEDD0D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Maybe you can set the allowed ips with listen_address in postgresql.conf. More,through network admin can achieve your aim more efficiency. > =E5=9C=A8 2025=E5=B9=B49=E6=9C=8812=E6=97=A5=EF=BC=8C00:21=EF=BC=8CRon Joh= nson =E5=86=99=E9=81=93=EF=BC=9A >=20 > =EF=BB=BF > PG 17.latest >=20 > My server has two IP addresses: > 10.1.2.3.4 > 10.1.2.3.5 (a VIP) >=20 > Some connections should only come in through the VIP, while others (like r= eplication) must come in through .4 and others (f.e. administrators, can com= e in from .4 or .5). >=20 > Is there any way to restrict that? I don't see anything in https://www.po= stgresql.org/docs/17/auth-pg-hba-conf.html but may be overlooking something.= >=20 > (Why don't we use a connection pooler? The 3rd party application has only= been validated against direct connections to PG. Bugs in PgPool caused prob= lems in prod.) >=20 > --=20 > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! --Apple-Mail-576B0BCC-B7A1-41C6-826D-D9B3B7FEDD0D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Maybe you can set the allowed ips with l= isten_address in postgresql.conf.

More,through network ad= min can achieve your aim more efficiency.

=E5=9C=A8 2025=E5=B9=B49=E6=9C=8812=E6=97=A5=EF=BC=8C00:21=EF= =BC=8CRon Johnson <ronljohnsonjr@gmail.com> =E5=86=99=E9=81=93=EF=BC=9A=

=EF=BB= =BF
PG 17.latest

My server has= two IP addresses:
10.1.2.3.4
10.1.2.3.5 (a VIP)

Some connections should only come in through the VIP, whil= e others (like replication) must come in through .4 and others (f.e. adminis= trators, can come in from .4 or .5).

Is there any w= ay to restrict that?  I don't see anything in https://www.postgresql.org/= docs/17/auth-pg-hba-conf.html but may be overlooking something.

(Why don't we use a connection pooler?  The 3rd party a= pplication has only been validated against direct connections to PG. Bu= gs in PgPool caused problems in prod.)

--
Death to <Redac= ted>, and butter sauce.
Don't boil me, I'm still alive.
= <Redacted> lobster!
= --Apple-Mail-576B0BCC-B7A1-41C6-826D-D9B3B7FEDD0D--