| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: cuckoo is hung during regression test |
| Date: | 2007-02-13 19:59:12 |
| Message-ID: | 20070213195912.GH23415@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Jim Nasby <jim(at)nasby(dot)net> writes:
> > On Feb 13, 2007, at 12:15 PM, Tom Lane wrote:
> >> We could possibly sleep() a bit before retrying,
> >> just to not suck 100% CPU, but that doesn't really *fix* anything ...
>
> > Well, not only that, but the machine is currently writing to the
> > postmaster log at the rate of 2-3MB/s. ISTM some kind of sleep
> > (perhaps growing exponentially to some limit) would be a good idea.
>
> Well, since the code has always behaved that way and no one noticed
> before, I don't think it's worth anything as complicated as a variable
> delay. I just stuck a fixed 100msec delay into the accept-failed code
> path.
Seems worth mentioning that bgwriter sleeps 1 sec in case of failure.
(And so does the autovac code I'm currently looking at).
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-02-13 20:05:24 | Re: cuckoo is hung during regression test |
| Previous Message | Bruce Momjian | 2007-02-13 19:56:33 | Re: DROP DATABASE and prepared xacts |