Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 22ff5c9

Browse files
doc: Clarify where ereport severity levels are defined
For a reader unfamiliar with the postgres code it might take some grepping to find where elevels are defined. This adds a reference to elog.h in the text like how SQLSTATE errorcodes are referenced to errcodes.h on the same page. Author: Kuwamura Masaki <kuwamura@db.is.i.nagoya-u.ac.jp> Discussion: https://postgr.es/m/CAMyC8qqp1UDA9zothnJ9CbUYByytwpALS3LkdZ6bs1w5kZw5Xg@mail.gmail.com
1 parent c4a1933 commit 22ff5c9

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

doc/src/sgml/sources.sgml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,8 @@ less -x4
105105

106106
<para>
107107
There are two required elements for every message: a severity level
108-
(ranging from <literal>DEBUG</literal> to <literal>PANIC</literal>) and a primary
108+
(ranging from <literal>DEBUG</literal> to <literal>PANIC</literal>, defined
109+
in <filename>src/include/utils/elog.h</filename>) and a primary
109110
message text. In addition there are optional elements, the most
110111
common of which is an error identifier code that follows the SQL spec's
111112
SQLSTATE conventions.

0 commit comments

Comments
 (0)