Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0E0609FB8C4 for ; Fri, 17 Aug 2007 08:43:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 99962-01-4 for ; Fri, 17 Aug 2007 08:43:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by postgresql.org (Postfix) with ESMTP id 9F64D9FB90B for ; Fri, 17 Aug 2007 08:35:48 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id v27so211379wah for ; Fri, 17 Aug 2007 04:35:47 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=msTuLmx+1tdL/x8KPPZzegkjypbwfxNriDjBFwAvCAeyHY4AX2HBWZdGbshGmk0KMVjC4K7JsdtLJ9UMOZ29YP2+2ZHXwLz2fqDGWlo2lyTDPplY0VVAwxeP8F/iCD97iL/6EOQsdQ+O60FBTxiMsrb6mo08PMHDpm9ewH36tWU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=CF+SWyfbevKZe9csU2VPRpaHmG1EPCcLmjTp2Gy2pJA+QEhU23J9PntFKuSHK3g5u19A1bi0Y+5DumTVPuZuUQCPCjS35IqwKD4LO/f+Cu1M5K2ZgbtgeCKviHNNfGZzIJGBA3pLZXW6C53hbG+6R4rxrq/e0gDAVf2fRntbWAs= Received: by 10.114.110.1 with SMTP id i1mr2180447wac.1187350107687; Fri, 17 Aug 2007 04:28:27 -0700 (PDT) Received: by 10.114.134.18 with HTTP; Fri, 17 Aug 2007 04:28:27 -0700 (PDT) Message-ID: Date: Fri, 17 Aug 2007 08:28:27 -0300 From: "Hilton Perantunes" To: pgsql-admin@postgresql.org Subject: Re: Yet Another Socket .s.PGSQL.5432 Problem In-Reply-To: <200708171109.25370.peter_e@gmx.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_73640_8241629.1187350107608" References: <20070816212517.GC27775@alvh.no-ip.org> <200708171109.25370.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/202 X-Sequence-Number: 26533 ------=_Part_73640_8241629.1187350107608 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Exactly what happened, Peter. Something was preventing me of successfully install 8.2.4 through apt-get, so I did it by hand. I'll read the documentation about LD_LIBRARY_PATH. Thank you. Hilton Perantunes On 8/17/07, Peter Eisentraut wrote: > > Am Donnerstag, 16. August 2007 23:41 schrieb Hilton Perantunes: > > Alvaro, it works like a charm =3D). Thank you all. > > > > Bad, bad Debian.. no cookies for you (and I'll read the error messages > more > > carefully next time)! > > The problem is quite likely some variant on the following: You had your > distribution-supplied PostgreSQL packages installed, which > use /var/run/postgresql as the socket location. Then you built your own > pieces of PostgreSQL, which use /tmp. When you call just "psql" > or "pgadmin3", they will use the system-supplied libpq, which uses the > system-specific socket location, since they don't know about your > hand-crafted installation. If you had called the psql binary from your > own > installation with an explicit path (and your used the rpath feature durin= g > compilation), then this would have worked. Or you could have used the > environment variable LD_LIBRARY_PATH to point to the libpq of your choice= . > There are a few ways to get this wrong. On Debian the socket location is > usually the first indicator, but you ought to be careful in general if yo= u > mix installations like that. > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ > --=20 Hilton William Ganzo Perantunes Sistemas de Informa=E7=E3o - Universidade Federal de Santa Catarina -- Dinheiro n=E3o traz felicidade, mas d=E1 uma sensa=E7=E3o t=E3o parecida...= -_- ------=_Part_73640_8241629.1187350107608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Exactly what happened, Peter. Something was preventing me of successfully i= nstall 8.2.4 through apt-get, so I did it by hand.

I'll read the= documentation about LD_LIBRARY_PATH.

Thank you.

Hilton Peran= tunes


On 8/17/07, Peter Eisentraut <pet= er_e@gmx.net> wrote:
Am Donnerstag, 16. August 2007 23:41 schrieb Hilton Perantunes:
> Alv= aro, it works like a charm =3D). Thank you all.
>
> Bad, bad De= bian.. no cookies for you (and I'll read the error messages more
>= ; carefully next time)!

The problem is quite likely some variant on the following: &nb= sp;You had your
distribution-supplied PostgreSQL packages installed, whi= ch
use /var/run/postgresql as the socket location.  Then you b= uilt your own
pieces of PostgreSQL, which use /tmp.  When you call just "p= sql"
or "pgadmin3", they will use the system-supplied lib= pq, which uses the
system-specific socket location, since they don't= know about your
hand-crafted installation.  If you had called the psql binary= from your own
installation with an explicit path (and your used the rpa= th feature during
compilation), then this would have worked.  = Or you could have used the
environment variable LD_LIBRARY_PATH to point to the libpq of your choi= ce.
There are a few ways to get this wrong.  On Debian the soc= ket location is
usually the first indicator, but you ought to be careful= in general if you
mix installations like that.

--
Peter Eisentraut
http://developer.postgresql.o= rg/~petere/



--
Hilt= on William Ganzo Perantunes
Sistemas de Informa=E7=E3o - Universidade Federal de Santa Catarina
= --
Dinheiro n=E3o traz felicidade, mas d=E1 uma sensa=E7=E3o t=E3o parec= ida...  -_- ------=_Part_73640_8241629.1187350107608--