<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgresql on LinuxHosted.com</title><link>https://www.linuxhosted.com/tags/postgresql/</link><description>Recent content in Postgresql on LinuxHosted.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LinuxHosted.com</copyright><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxhosted.com/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>Install PostgreSQL on an Ubuntu VPS With Safe Remote Access</title><link>https://www.linuxhosted.com/post/how-to-install-postgresql-ubuntu-vps-remote-access/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.linuxhosted.com/post/how-to-install-postgresql-ubuntu-vps-remote-access/</guid><description>
&lt;p&gt;A fresh &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL&lt;/a&gt; install on &lt;a href="https://ubuntu.com/server"&gt;Ubuntu&lt;/a&gt; accepts connections from the local system only. The &lt;a href="https://www.postgresql.org/docs/current/runtime-config-connection.html"&gt;&lt;code&gt;listen_addresses&lt;/code&gt; setting defaults to &lt;code&gt;localhost&lt;/code&gt;&lt;/a&gt;, which allows TCP connections over the loopback interface and nothing else. On a VPS with a public IP address, that is the right state to start from.&lt;/p&gt;
&lt;p&gt;Opening the database to a remote application server takes four changes, in this order: a non-superuser role with a SCRAM password and its own database, a listener on the right interface, a &lt;code&gt;pg_hba.conf&lt;/code&gt; rule that requires TLS from one known address, and a firewall rule for port 5432. The &lt;code&gt;postgres&lt;/code&gt; superuser stays local.&lt;/p&gt;</description></item></channel></rss>