| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: PATCH to allow concurrent VACUUMs to not lock each |
| Date: | 2005-08-17 19:40:53 |
| Message-ID: | 5805.1124307653@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Just for the archives, attached is as far as I'd gotten with cleaning up
Hannu's patch before I realized that it wasn't doing what it needed to
do. This fixes an end-of-transaction race condition (can't unset
inVacuum before xact end, unless you want OldestXmin going backwards
from the point of view of other people) and improves the documentation
of what's going on. But unless someone can convince me that it's safe
to mess with GetSnapshotData, it's unlikely this'll ever get applied.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 15.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-17 19:54:07 | Re: do we need inet_ntop check? |
| Previous Message | Tom Lane | 2005-08-17 18:48:09 | Re: Missing CONCURRENT VACUUM (Was: Release notes for |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-17 19:46:22 | Re: Trivial patch, silence CC warnings |
| Previous Message | Alvaro Herrera | 2005-08-17 17:48:51 | Trivial patch, silence CC warnings |