Tom,
Thanks again. If you read the entire line you quoted, I was trying to confirm that intrinsic features and utilities, including pg_dump, don't use any **other** network ports, not that they didn't use any at all.
It seems less likely with every exchange that a listing of network ports used/needed does exist. That's a shame.
I guess if I find myself in the situation where I really need that listing, I'll have to dust off my *extremely* rusty C skills and pour through the source code.
Thanks to everyone for taking the time to chime in.
Until next time,
rik.
On Thu, Aug 11, 2022 at 10:13 AM Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
richard coleman <rcoleman.ascentgl@xxxxxxxxx> writes:
> Is it correct to state that (barring the soon to be obsolete stats
> collector):
> - PostgreSQL only uses the configured port, who's default is 5432, via
> tcp
> - outgoing connections are all tcp and use random ports
There are no outgoing connections in basic PG, unless maybe you
enable log_hostname, and then it'd depend on what your libc does
for DNS lookup --- but that'd more likely be UDP than TCP.
> - none of the other intrinsic features; replication, pg_dump,
> pg_basebackup, pg_restore, etc. use any other network ports
Replication surely requires some sort of connection, although it
could be either outgoing or incoming depending on your setup.
I'm also getting rather confused by what you mean by "use a port",
if you think that clients such as pg_dump don't.
> - network ports used by extensions, even if included in the base
> install, are beyond the scope of PostgreSQL documentation
If we were to start adding this sort of info to the docs,
it'd be appropriate to document the behavior of each included
extension in the documentation file for that extension.
As I go through these examples, though, I grow less enthusiastic
about it being a useful exercise at all.
regards, tom lane
