Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit22ff5c9

Browse files
doc: Clarify where ereport severity levels are defined
For a reader unfamiliar with the postgres code it might take somegrepping to find where elevels are defined. This adds a referenceto elog.h in the text like how SQLSTATE errorcodes are referencedto 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 parentc4a1933 commit22ff5c9

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)
[8]ページ先頭
©2009-2025 Movatter.jp