| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | "Hamedany, Allen" <Allen(dot)Hamedany(at)revivio(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: createdb fails |
| Date: | 2004-02-03 15:16:26 |
| Message-ID: | 17943.1075821386@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kris Jurka <books(at)ejurka(dot)com> writes:
> What happens if you add a sleep 5 call in between the createdb calls?
Even a fractional-second sleep would likely do it. I have traced
through scenarios like this in the past, and AFAICT the exiting backend
is not doing anything wrong or even using an unreasonable amount of
CPU time before it quits. It simply isn't getting scheduled to run
because for one reason or another the kernel gives time slices to the
foreground clients and the new backend first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2004-02-03 22:21:44 | [Magic OnLine] Suppression du Virus: Server Report |
| Previous Message | Kris Jurka | 2004-02-03 11:49:59 | Re: createdb fails |