| commit | 9ee50ef1b62b55153162b86d11892db4ae95e47d | |
| author | heikki <heikki> | |
| Mon, 11 Aug 2008 11:05:11 +0000 (11 11:05 +0000) | ||
| committer | heikki <heikki> | |
| Mon, 11 Aug 2008 11:05:11 +0000 (11 11:05 +0000) | ||
| tree | 74301d6029547847bec7ec4bf4af950853b6ebd0 | treesnapshot (tar.gz zip) |
| parent | b147ccd420f0adfd526e681beffccfd370bacfad | commitdiff |
Introduce the concept of relation forks. An smgr relation can now consist
of multiple forks, and each fork can be created and grown separately.
The bulk of this patch is about changing the smgr API to include an extra
ForkNumber argument in every smgr function. Also, smgrscheduleunlink and
smgrdounlink no longer implicitly call smgrclose, because other forks might
still exist after unlinking one. The callers of those functions have been
modified to call smgrclose instead.
This patch in itself doesn't have any user-visible effect, but provides the
infrastructure needed for upcoming patches. The additional forks envisioned
are a rewritten FSM implementation that doesn't rely on a fixed-size shared
memory block, and a visibility map to allow skipping portions of a table in
VACUUM that have no dead tuples.
of multiple forks, and each fork can be created and grown separately.
The bulk of this patch is about changing the smgr API to include an extra
ForkNumber argument in every smgr function. Also, smgrscheduleunlink and
smgrdounlink no longer implicitly call smgrclose, because other forks might
still exist after unlinking one. The callers of those functions have been
modified to call smgrclose instead.
This patch in itself doesn't have any user-visible effect, but provides the
infrastructure needed for upcoming patches. The additional forks envisioned
are a rewritten FSM implementation that doesn't rely on a fixed-size shared
memory block, and a visibility map to allow skipping portions of a table in
VACUUM that have no dead tuples.
31 files changed: