diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-02-01 19:10:30 +0000 |
| commit | 8b4ff8b6a14096a28910fbff3d485f30dcb9a637 (patch) | |
| tree | c250f17f4a8e3bfee442970a0666431ed8310650 /contrib/tsearch2/tsvector.c | |
| parent | baaec74c5a953032049015883802660edd821cac (diff) | |
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
Diffstat (limited to 'contrib/tsearch2/tsvector.c')
| -rw-r--r-- | contrib/tsearch2/tsvector.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/tsearch2/tsvector.c b/contrib/tsearch2/tsvector.c index 1abf1914e33..f4e83ec1496 100644 --- a/contrib/tsearch2/tsvector.c +++ b/contrib/tsearch2/tsvector.c @@ -859,7 +859,7 @@ tsearch2(PG_FUNCTION_ARGS) trigdata = (TriggerData *) fcinfo->context; if (TRIGGER_FIRED_FOR_STATEMENT(trigdata->tg_event)) /* internal error */ - elog(ERROR, "TSearch: Can't process STATEMENT events"); + elog(ERROR, "TSearch: Cannot process STATEMENT events"); if (TRIGGER_FIRED_AFTER(trigdata->tg_event)) /* internal error */ elog(ERROR, "TSearch: Must be fired BEFORE event"); |