From 5f9869d0ee1ec8b4d45cc50334cd8c5582969f3b Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 7 Nov 2007 12:24:24 +0000 Subject: Use "alternative" instead of "alternate" where it is clearer. --- src/backend/access/common/heaptuple.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/access/common/heaptuple.c') diff --git a/src/backend/access/common/heaptuple.c b/src/backend/access/common/heaptuple.c index f1a80d6feee..a6dab8da121 100644 --- a/src/backend/access/common/heaptuple.c +++ b/src/backend/access/common/heaptuple.c @@ -57,7 +57,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.117 2007/04/06 04:21:41 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/access/common/heaptuple.c,v 1.118 2007/11/07 12:24:23 petere Exp $ * *------------------------------------------------------------------------- */ @@ -489,7 +489,7 @@ heap_attisnull(HeapTuple tup, int attnum) * * This caches attribute offsets in the attribute descriptor. * - * An alternate way to speed things up would be to cache offsets + * An alternative way to speed things up would be to cache offsets * with the tuple, but that seems more difficult unless you take * the storage hit of actually putting those offsets into the * tuple you send to disk. Yuck. -- cgit v1.2.3