Re: Fix overflow of bgwriter's request queue

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: Fix overflow of bgwriter's request queue
Date: 2006-01-13 22:20:14
Message-ID: 14418.1137190814@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:
> Maybe the take a copied list is safer. I got a little afraid of doing
> seqscan hash while doing HASH_ENTER at the same time. Do we have this kind
> of hash usage somewhere?

Sure, it's perfectly safe. It's unspecified whether the scan will visit
such entries or not (because it might or might not already have passed
their hash bucket), but per above discussion we don't really care.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Jaime Casanova 2006-01-14 04:53:20 message for constraint
Previous Message Qingqing Zhou 2006-01-13 22:09:50 Re: Fix overflow of bgwriter's request queue