Commit 2011bebc authored by Tom Lane's avatar Tom Lane

Use 'token' not 'lexeme' to describe the output of a parser.

parent 56303abf
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
* *
* Copyright (c) 2000-2007, PostgreSQL Global Development Group * Copyright (c) 2000-2007, PostgreSQL Global Development Group
* *
* $PostgreSQL: pgsql/src/bin/psql/describe.c,v 1.159 2007/08/22 02:25:34 tgl Exp $ * $PostgreSQL: pgsql/src/bin/psql/describe.c,v 1.160 2007/10/16 18:02:26 tgl Exp $
*/ */
#include "postgres_fe.h" #include "postgres_fe.h"
#include "describe.h" #include "describe.h"
...@@ -2101,7 +2101,7 @@ describeOneTSParser(const char *oid, const char *nspname, const char *prsname) ...@@ -2101,7 +2101,7 @@ describeOneTSParser(const char *oid, const char *nspname, const char *prsname)
_("Get next token"), oid, _("Get next token"), oid,
_("End parse"), oid, _("End parse"), oid,
_("Get headline"), oid, _("Get headline"), oid,
_("Get lexeme types"), oid _("Get token types"), oid
); );
res = PSQLexec(buf.data, false); res = PSQLexec(buf.data, false);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment