Bug 158969 - TCP/IP connections disabled by default
TCP/IP connections disabled by default
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: postgresql (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Lane
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-27 07:08 EDT by Murray Cumming
Modified: 2013-07-02 23:05 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-27 11:26:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Murray Cumming 2005-05-27 07:08:09 EDT
The default
  /var/lib/pgsql/data/postgresql.conf
has
  #tcpip_socket = false
and must be changed to
  tcpip_socket = true
to allow TCP/IP connections, even from applications on the localhost.

This is rather annoying, and difficult for non-technical users to do when
installing applications such as Glom. By the way, debian activates this by default.
Comment 1 Tom Lane 2005-05-27 11:26:10 EDT
This is following the default upstream behavior, which I'm disinclined to have
the RPM editorialize on in any significant fashion.  Loosening the connection
restrictions from what users expect from the PostgreSQL documentation could
result in unexpected security holes.

FWIW, Postgres 8.0 does allow local TCP connections by default, so FC4 will act
the way you want.  But I think it's a bad idea to change it in FC3.

Note You need to log in before you can comment on or make changes to this bug.