| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ed Loehr <ed(at)LoehrTech(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: backend exit mystery |
| Date: | 2003-10-14 21:04:19 |
| Message-ID: | 9569.1066165459@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ed Loehr <ed(at)LoehrTech(dot)com> writes:
> Attached is a small C program that reliably reproduces this=20
> problem on the setup above. I added an explicit timeout to PQconnectdb()=
> to wait only 30 seconds. I'm curious to know if anyone can easily repeat=
> the problem (careful, it will generate a bit of traffic, cpu load, and run=
> forever). My last example run showed 17 timeouts seemingly randomly=20
> dispersed among 5000 consecutive connection attempts.=20=20
I tried to duplicate the problem, without success --- 20000 connection
attempts without failure. Setup is HPUX 10.20 client, RHL8 server
(2.4.18-24.8.0 kernel); but it's a single-processor machine, not dual as
in your example. I was using CVS-tip PG sources, also.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-10-14 21:07:05 | Re: Virtual Machines and postgres |
| Previous Message | Jan Wieck | 2003-10-14 20:59:41 | Re: Excute comnands OS from plpgsql |