From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Skipping VACUUM of indexes when no work required |
Date: | 2006-02-11 23:36:51 |
Message-ID: | 29381.1139701011@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Here's the patch as-applied. Note one major difference from your
original: the logic about whether an indexscan can be skipped is now
entirely local to the index AMs, rather than allowing VACUUM to make
assumptions that may not be warranted for particular AMs. For the
same reason, the AM is still responsible for providing the tuple
count statistic.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
bulkdelete.patch.gz | application/octet-stream | 3.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-12 00:21:45 | Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed) |
Previous Message | Martijn van Oosterhout | 2006-02-11 23:26:55 | Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed) |