| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Nik" <XLPizza(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Connections not closing |
| Date: | 2006-01-19 21:43:03 |
| Message-ID: | 9413.1137706983@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Nik" <XLPizza(at)gmail(dot)com> writes:
> Ok, I simplified the problem. I tried just running psql from the
> command line, and I noticed that it opens two connection on two
> different ports, and it closes only one.
> For example I do the following in the command prompt:
> C:\> psql -h host_name -p 5432 -d db_name -U user_name
> Password:
> 2006-01-19 09:50:29 [unknown] LOG: connection received: host=client1
> port=3775
> 2006-01-19 09:50:31 [unknown] LOG: connection received: host=client1
> port=3778
> 2006-01-19 09:50:31 test LOG: connection authorized: user=user_name
> database=db_name
It tries to connect, gets told it needs a password (the log verbosity
level is not high enough to record the rejection), asks you for the
password, and connects again. I don't see anything funny here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-01-19 21:56:17 | Re: [PATCH] Better way to check for getaddrinfo function. |
| Previous Message | Bruce Momjian | 2006-01-19 21:30:11 | Re: pg_dump throws no buffer space available error |