| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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 20:07:54 |
| Message-ID: | 8713.1171397274@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Alvaro Herrera wrote:
>> Tom Lane wrote:
>>> 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).
> There is probably a good case for a shorter delay in postmaster, though.
Yeah, that's what I thought. We don't really care if either bgwriter or
autovac goes AWOL for a little while, but if the postmaster's asleep
then nobody can connect.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-13 22:55:11 | Re: NULL and plpgsql rows |
| Previous Message | Andrew Dunstan | 2007-02-13 20:05:24 | Re: cuckoo is hung during regression test |