Your message dated Sun, 19 Jun 2005 01:38:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line python-pgsql: Can't connect to UNIX socket with postgresql-7.4
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Jun 2005 12:53:05 +0000
>From [EMAIL PROTECTED] Fri Jun 10 05:53:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Dgj0T-0004Ln-00; Fri, 10 Jun 2005 05:53:05 -0700
Received: from hoshi.netintact.se ([127.0.0.1]) [217.73.97.28] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Dgj0R-0002Wd-00; Fri, 10 Jun 2005 07:53:03 -0500
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
From: Thomas Nilsson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-pgsql: Can't connect to UNIX socket with postgresql-7.4
X-Mailer: reportbug 3.12
Date: Fri, 10 Jun 2005 14:52:49 +0200
X-Debbugs-Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-9.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        OUR_MTA_MSGID,X_DEBBUGS_CC autolearn=ham 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: python-pgsql
Version: 2.4.0-5
Severity: grave
Justification: causes non-serious data loss


After upgrading to postgresql-7.4 it's no longer possible to connect to
the UNIX socket, only connections over tcpip are working.

In [10]: conn = PgSQL.connect(database="database", user="username")
---------------------------------------------------------------------------
libpq.DatabaseError                             Traceback (most recent call 
last)

/home/fatal/<console> 

/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py in connect(dsn, user, 
password, host, database, port, options, tty, client_encoding, unicode_results)
   2209         connInfo = "%s%s=%s " % (connInfo, i, _d[i])
   2210 
-> 2211     return Connection(connInfo, client_encoding, unicode_results)
   2212 
   2213 def _handleArray(value):

/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py in __init__(***failed 
resolving arguments***)
   2329             self.__dict__["_isOpen"] = None
   2330             del(self)
-> 2331             raise DatabaseError, m
   2332             
   2333         self.__dict__["autocommit"] = 0

DatabaseError: could not connect to 
server:����8�b���������������Q
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

In [12]: conn = PgSQL.connect(database="database", user="user", 
host="localhost")

In [13]: conn.version
Out[13]: PostgreSQL 7.4.8 on i386-pc-linux-gnu, compiled by GCC cc (GCC) 3.3.5 
(Debian 1:3.3.5-13)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.6-win4lin-ftl1
Locale: LANG=C, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)

Versions of packages python-pgsql depends on:
ii  python                        2.3.5-2    An interactive high-level object-o
ii  python2.3-pgsql               2.4.0-5    A Python DB-API 2.0 interface to P

-- no debconf information

---------------------------------------
Received: (at 312847-done) by bugs.debian.org; 19 Jun 2005 08:38:08 +0000
>From [EMAIL PROTECTED] Sun Jun 19 01:38:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DjvJg-0005SD-00; Sun, 19 Jun 2005 01:38:08 -0700
Received: by mauritius.dodds.net (Postfix, from userid 1000)
        id 3133EA4467; Sun, 19 Jun 2005 01:38:08 -0700 (PDT)
Date: Sun, 19 Jun 2005 01:38:08 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: python-pgsql: Can't connect to UNIX socket with postgresql-7.4
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

This bug (in libpq4) has been fixed with the upload of postgresql-8.0
8.0.3-6.

Thanks,
--=20
Steve Langasek
postmodern programmer

--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCtS7vKN6ufymYLloRAnXGAKCy4PSKJOa0FNnmBzF8+aH07wrnfACfV7LS
9RdCUeyYPLmYpwlfJ3xHZgk=
=I8UC
-----END PGP SIGNATURE-----

--ReaqsoxgOBHFXBhH--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to