Re: [GENERAL] Unable to connect to a dabase

2006-01-16 Thread Jim C. Nasby
On Sat, Jan 14, 2006 at 04:28:39AM +, Sally Sally wrote: > Yes a backend gets spewed. Actually it did connect me finally (I am not > sure exactly how long it took). I checked back after about four hours and I > was connected. I have also noticed in the past that after running vacuum > the cl

Re: [GENERAL] Unable to connect to a dabase

2006-01-13 Thread Sally Sally
From: "Joshua D. Drake" <[EMAIL PROTECTED]> To: Jim Nasby <[EMAIL PROTECTED]> CC: Sally Sally <[EMAIL PROTECTED]>, pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to a dabase Date: Fri, 13 Jan 2006 16:02:11 -0800 LOG: database system was shut

Re: [GENERAL] Unable to connect to a dabase

2006-01-13 Thread Joshua D. Drake
et to localhost 5432 is it listening or does it hang? If it hangs I would guess a firewall but I would think you would pick up on the unix socket. J From: "Jim C. Nasby" <[EMAIL PROTECTED]> To: Sally Sally <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GE

Re: [GENERAL] Unable to connect to a dabase

2006-01-13 Thread Jim Nasby
getting a stack trace of psql trying to connect would shed some light... Does a backend get spawned when you try running psql? (Look at ps aux|grep postgres before and after running psql). > >From: "Jim C. Nasby" <[EMAIL PROTECTED]> > >To: Sally Sally <[EMAIL PRO

Re: [GENERAL] Unable to connect to a dabase

2006-01-13 Thread Sally Sally
I'm sorry that was not intentional. From: "Jim C. Nasby" <[EMAIL PROTECTED]> To: Sally Sally <[EMAIL PROTECTED]> CC: pgsql-general@postgresql.org Subject: Re: [GENERAL] Unable to connect to a dabase Date: Fri, 13 Jan 2006 16:55:16 -0600 Please don't hijack t

Re: [GENERAL] Unable to connect to a dabase

2006-01-13 Thread Jim C. Nasby
Please don't hijack threads fo new questions. On Fri, Jan 13, 2006 at 10:45:51PM +, Sally Sally wrote: > I had to kill a vacuum in the middle with -9. I shut down and restarted the > postgres server several times after that but I am unable to connect to the > db that I was initially running