From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | HOT add-on patch |
Date: | 2007-09-15 18:51:19 |
Message-ID: | 2e78013d0709151151od465e2eo247760ab57d0c866@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Hi All,
This patch is an add-on patch the version 15 posted earlier and
should be applied on top of version 15. The following review items
has been fixed:
- Fix the pruning code to prune all tuples upto and including the
latest DEAD tuple in the chain.
- Removed the heap tuple freezing changes because they are
no longer required because of changes to the pruning code
- Removed the HeapTupleSatisfiesAbort() code. We now collect
all DEAD heap-only tuples while scanning the page. A separate
bitmap is used to avoid duplicate entries in the deadtups array.
This is required because a DEAD HOT tuple may be scanned twice,
once while traversing the chain and then directly.
- A little improvement to the WAL logging in heap_page_prune_defrag().
Earlier we were logging two WAL records, now we do that only once
- The autoanalyze code now treats redirect dead line pointers as dead
rows.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
HOT-v15-16.patch.gz | application/x-gzip | 10.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-15 21:59:09 | HOT synced with HEAD |
Previous Message | Stefan Kaltenbrunner | 2007-09-15 17:24:27 | Re: PL/TCL Patch to prevent postgres from becoming multithreaded |