aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/cluster.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-06-09 14:32:50 -0400
committerBruce Momjian <bruce@momjian.us>2011-06-09 14:32:50 -0400
commit6560407c7db2c7e32926a46f5fb52175ac10d9e5 (patch)
tree9641e538893819410634624a8e0cb86a13d857a6 /src/backend/commands/cluster.c
parentadf43b2b36ca3d7f988933990051c74a4bd0d6f8 (diff)
downloadpostgresql-6560407c7db2c7e32926a46f5fb52175ac10d9e5.tar.gz
postgresql-6560407c7db2c7e32926a46f5fb52175ac10d9e5.zip
Pgindent run before 9.1 beta2.
Diffstat (limited to 'src/backend/commands/cluster.c')
-rw-r--r--src/backend/commands/cluster.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 0ab3a8bcfae..c020dc2e4ec 100644
--- a/src/backend/commands/cluster.c
+++ b/src/backend/commands/cluster.c
@@ -762,12 +762,12 @@ copy_heap_data(Oid OIDNewHeap, Oid OIDOldHeap, Oid OIDOldIndex,
/*
* If the OldHeap has a toast table, get lock on the toast table to keep
- * it from being vacuumed. This is needed because autovacuum processes
+ * it from being vacuumed. This is needed because autovacuum processes
* toast tables independently of their main tables, with no lock on the
- * latter. If an autovacuum were to start on the toast table after we
+ * latter. If an autovacuum were to start on the toast table after we
* compute our OldestXmin below, it would use a later OldestXmin, and then
* possibly remove as DEAD toast tuples belonging to main tuples we think
- * are only RECENTLY_DEAD. Then we'd fail while trying to copy those
+ * are only RECENTLY_DEAD. Then we'd fail while trying to copy those
* tuples.
*
* We don't need to open the toast relation here, just lock it. The lock