| From: | Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Subject: | remove lock protection on HeapTupleSatisfiesVacuum |
| Date: | 2006-06-06 02:35:12 |
| Message-ID: | Pine.LNX.4.58.0606052227580.862@eon.cs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Attached is a patch to remove the lock protection for
HeapTupleSatisfiesVacuum() in index code. The basic idea is: if we can do
a pin/lock/unlock sequence on a page, then without locking again, we are
gauranteed that there is no vacuum process acting on the same page.
According to buffer pool access rule #4, we then can examine/change the
hints bit safely.
Regards,
Qingqing
| Attachment | Content-Type | Size |
|---|---|---|
| index.diff | text/plain | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ITAGAKI Takahiro | 2006-06-06 02:45:14 | fillfactor using WITH syntax |
| Previous Message | Tom Lane | 2006-06-05 17:58:27 | Re: Allow commenting of variables in postgresql.conf to - |