{"id":7666,"date":"2026-03-19T07:47:08","date_gmt":"2026-03-19T12:47:08","guid":{"rendered":"https:\/\/www.logikalsolutions.com\/wordpress\/?p=7666"},"modified":"2026-03-19T07:47:09","modified_gmt":"2026-03-19T12:47:09","slug":"fedora-43","status":"publish","type":"post","link":"https:\/\/www.logikalsolutions.com\/wordpress\/information-technology\/fedora-43\/","title":{"rendered":"Fedora 43 and Postgresql"},"content":{"rendered":"\n

While Fedora 43 has a fairly clean look, it once again goes to great lengths to be “expert friendly.” This particular battle has to do with Postgresql. Regular readers may recall my post about getting Postgresql to install and run on Fedora 33<\/a>. Most of that post is still relevant.<\/p>\n\n\n\n

fedora 43 postgresql Error: connection to server at “localhost” (::1), port 5432 failed: FATAL:<\/h2>\n\n\n\n

Yeah, most of you found this post because of that error. With the exception of PCLinuxOS, the RPM based distro world has a fetish for not playing nice with others. When you choose to do something none of the popular distros do, you should at least have the decency to spit out a message during installation.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

The “defaults” used by most platforms are commented out on Fedora 43. You need to tell Postgresql to listen to localhost on port 5432, where everybody<\/em> looks for it.<\/p>\n\n\n\n

That is Still Not Enough<\/h2>\n\n\n\n

Even after you change that and reboot you still cannot connect over local host using a password. Search your system for<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span>