Re: Change BgWriterCommLock to spinlock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Change BgWriterCommLock to spinlock
Date: 2006-01-09 01:08:26
Message-ID: 24503.1136768906@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> Do you suggest it makes sense that we continue to work on the patch or let
> it be?

I don't see any problem here that urgently needs solving. If we ever
see any reports of out-of-memory failures in the bgwriter, then it'll
be time to worry about this, but I think it quite unlikely that we
ever will. (Even if we do, a simpler answer would be to increase
the initial size of the pending-requests hashtable.)

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Qingqing Zhou 2006-01-09 01:13:25 Re: Change BgWriterCommLock to spinlock
Previous Message Qingqing Zhou 2006-01-09 01:01:59 Re: Change BgWriterCommLock to spinlock