diff options
Diffstat (limited to 'src/backend/access/index/genam.c')
| -rw-r--r-- | src/backend/access/index/genam.c | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/src/backend/access/index/genam.c b/src/backend/access/index/genam.c index bd280360879..d95fd90a424 100644 --- a/src/backend/access/index/genam.c +++ b/src/backend/access/index/genam.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/access/index/genam.c,v 1.80 2010/02/07 20:48:09 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/access/index/genam.c,v 1.81 2010/02/26 02:00:33 momjian Exp $ * * NOTES * many of the old access method routines have been turned into @@ -94,13 +94,13 @@ RelationGetIndexScan(Relation indexRelation, /* * During recovery we ignore killed tuples and don't bother to kill them - * either. We do this because the xmin on the primary node could easily - * be later than the xmin on the standby node, so that what the primary + * either. We do this because the xmin on the primary node could easily be + * later than the xmin on the standby node, so that what the primary * thinks is killed is supposed to be visible on standby. So for correct * MVCC for queries during recovery we must ignore these hints and check - * all tuples. Do *not* set ignore_killed_tuples to true when running - * in a transaction that was started during recovery. - * xactStartedInRecovery should not be altered by index AMs. + * all tuples. Do *not* set ignore_killed_tuples to true when running in a + * transaction that was started during recovery. xactStartedInRecovery + * should not be altered by index AMs. */ scan->kill_prior_tuple = false; scan->xactStartedInRecovery = TransactionStartedDuringRecovery(); @@ -170,24 +170,24 @@ BuildIndexValueDescription(Relation indexRelation, for (i = 0; i < natts; i++) { - char *val; + char *val; if (isnull[i]) val = "null"; else { - Oid foutoid; - bool typisvarlena; + Oid foutoid; + bool typisvarlena; /* - * The provided data is not necessarily of the type stored in - * the index; rather it is of the index opclass's input type. - * So look at rd_opcintype not the index tupdesc. + * The provided data is not necessarily of the type stored in the + * index; rather it is of the index opclass's input type. So look + * at rd_opcintype not the index tupdesc. * * Note: this is a bit shaky for opclasses that have pseudotype - * input types such as ANYARRAY or RECORD. Currently, the - * typoutput functions associated with the pseudotypes will - * work okay, but we might have to try harder in future. + * input types such as ANYARRAY or RECORD. Currently, the + * typoutput functions associated with the pseudotypes will work + * okay, but we might have to try harder in future. */ getTypeOutputInfo(indexRelation->rd_opcintype[i], &foutoid, &typisvarlena); |