pgsql: Further tweak wording of error messages about bad CONTINUE/EXIT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Further tweak wording of error messages about bad CONTINUE/EXIT
Date: 2015-08-25 18:06:22
Message-ID: E1ZUIc2-000165-Jd@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Further tweak wording of error messages about bad CONTINUE/EXIT statements.

Per discussion, a little more verbosity seems called for.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/781ed2bfa35f0a8a7ad1029d3a7d7687c73d86a0

Modified Files
--------------
src/pl/plpgsql/src/pl_gram.y | 3 ++-
src/test/regress/expected/plpgsql.out | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-08-25 23:13:15 pgsql: Docs: be explicit about datatype matching for lead/lag functions
Previous Message Tom Lane 2015-08-25 17:09:54 pgsql: Limit the verbosity of memory context statistics dumps.