From 7386089d23c748af142ec7e3668fa0dd164eaf99 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Mon, 26 Mar 2012 11:03:06 -0400 Subject: Code cleanup for heap_freeze_tuple. It used to be case that lazy vacuum could call this function with only a shared lock on the buffer, but neither lazy vacuum nor any other code path does that any more. Simplify the code accordingly and clean up some related, obsolete comments. --- src/backend/access/heap/rewriteheap.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'src/backend/access/heap/rewriteheap.c') diff --git a/src/backend/access/heap/rewriteheap.c b/src/backend/access/heap/rewriteheap.c index 31b2b678b6c..9a8f05d9331 100644 --- a/src/backend/access/heap/rewriteheap.c +++ b/src/backend/access/heap/rewriteheap.c @@ -335,13 +335,8 @@ rewrite_heap_tuple(RewriteState state, /* * While we have our hands on the tuple, we may as well freeze any * very-old xmin or xmax, so that future VACUUM effort can be saved. - * - * Note we abuse heap_freeze_tuple() a bit here, since it's expecting to - * be given a pointer to a tuple in a disk buffer. It happens though that - * we can get the right things to happen by passing InvalidBuffer for the - * buffer. */ - heap_freeze_tuple(new_tuple->t_data, state->rs_freeze_xid, InvalidBuffer); + heap_freeze_tuple(new_tuple->t_data, state->rs_freeze_xid); /* * Invalid ctid means that ctid should point to the tuple itself. We'll -- cgit v1.2.3