mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
Re-run pgindent with updated list of typedefs. (Updated README should
avoid this problem in the future.)
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/access/heap/pruneheap.c,v 1.4 2007/11/15 21:14:32 momjian Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/access/heap/pruneheap.c,v 1.5 2007/11/15 22:25:15 momjian Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -75,11 +75,11 @@ heap_page_prune_opt(Relation relation, Buffer buffer, TransactionId OldestXmin)
|
||||
* fill-factor target (but not less than 10%).
|
||||
*
|
||||
* Checking free space here is questionable since we aren't holding any
|
||||
* lock on the buffer; in the worst case we could get a bogus answer.
|
||||
* It's unlikely to be *seriously* wrong, though, since reading either
|
||||
* pd_lower or pd_upper is probably atomic. Avoiding taking a lock seems
|
||||
* better than sometimes getting a wrong answer in what is after all just
|
||||
* a heuristic estimate.
|
||||
* lock on the buffer; in the worst case we could get a bogus answer. It's
|
||||
* unlikely to be *seriously* wrong, though, since reading either pd_lower
|
||||
* or pd_upper is probably atomic. Avoiding taking a lock seems better
|
||||
* than sometimes getting a wrong answer in what is after all just a
|
||||
* heuristic estimate.
|
||||
*/
|
||||
minfree = RelationGetTargetPageFreeSpace(relation,
|
||||
HEAP_DEFAULT_FILLFACTOR);
|
||||
|
Reference in New Issue
Block a user