1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Error and Notice Message Fields</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 HREF="mailto:pgsql-docs@postgresql.org"><LINK
12 TITLE="PostgreSQL 7.4.1 Documentation"
13 HREF="index.html"><LINK
15 TITLE="Frontend/Backend Protocol"
16 HREF="protocol.html"><LINK
18 TITLE="Message Formats"
19 HREF="protocol-message-formats.html"><LINK
21 TITLE="Summary of Changes since Protocol 2.0"
22 HREF="protocol-changes.html"><LINK
25 HREF="stylesheet.css"><META
27 CONTENT="2003-12-22T03:48:47"></HEAD
33 SUMMARY="Header navigation table"
43 >PostgreSQL 7.4.1 Documentation</TH
51 HREF="protocol-message-formats.html"
67 >Chapter 44. Frontend/Backend Protocol</TD
81 HREF="protocol-changes.html"
95 NAME="PROTOCOL-ERROR-FIELDS"
96 >44.5. Error and Notice Message Fields</A
99 >This section describes the fields that may appear in ErrorResponse and
100 NoticeResponse messages. Each field type has a single-byte identification
101 token. Note that any given field type should appear at most once per
115 > Severity: the field contents are
126 > (in an error message), or
143 > (in a notice message),
144 or a localized translation of one of these. Always present.</P
153 > Code: the SQLSTATE code for the error (see <A
154 HREF="errcodes-appendix.html"
156 >). Not localizable. Always present.</P
165 > Message: the primary human-readable error message.
166 This should be accurate but terse (typically one line).
176 > Detail: an optional secondary error message carrying more
177 detail about the problem. May run to multiple lines.</P
186 > Hint: an optional suggestion what to do about the problem.
187 This is intended to differ from Detail in that it offers advice
188 (potentially inappropriate) rather than hard facts.
189 May run to multiple lines.</P
198 > Position: the field value is a decimal ASCII integer, indicating
199 an error cursor position as an index into the original query string.
200 The first character has index 1, and positions are measured in
201 characters not bytes.</P
210 > Where: an indication of the context in which the error occurred.
211 Presently this includes a call stack traceback of active PL functions.
212 The trace is one entry per line, most recent first.</P
221 > File: the file name of the source-code location where the error
231 > Line: the line number of the source-code location where the error
241 > Routine: the name of the source-code routine reporting the error.</P
246 >The client is responsible for formatting displayed information to meet its
247 needs; in particular it should break long lines as needed. Newline characters
248 appearing in the error message fields should be treated as paragraph breaks,
256 SUMMARY="Footer navigation table"
267 HREF="protocol-message-formats.html"
285 HREF="protocol-changes.html"
309 >Summary of Changes since Protocol 2.0</TD