From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/error-message-reporting.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/error-message-reporting.html') diff --git a/doc/src/sgml/html/error-message-reporting.html b/doc/src/sgml/html/error-message-reporting.html index b0e42dc..612044c 100644 --- a/doc/src/sgml/html/error-message-reporting.html +++ b/doc/src/sgml/html/error-message-reporting.html @@ -1,5 +1,5 @@ -56.2. Reporting Errors Within the Server
56.2. Reporting Errors Within the Server
Prev UpChapter 56. PostgreSQL Coding ConventionsHome Next

56.2. Reporting Errors Within the Server

+56.2. Reporting Errors Within the Server

56.2. Reporting Errors Within the Server
Prev UpChapter 56. PostgreSQL Coding ConventionsHome Next

56.2. Reporting Errors Within the Server

Error, warning, and log messages generated within the server code should be created using ereport, or its older cousin elog. The use of this function is complex enough to @@ -247,4 +247,4 @@ ereport(level, errmsg_internal("format string", ...)); routines will not affect it. That would not be true if you were to write strerror(errno) explicitly in errmsg's parameter list; accordingly, do not do so. -

Prev Up Next
56.1. Formatting Home 56.3. Error Message Style Guide
\ No newline at end of file +

Prev Up Next
56.1. Formatting Home 56.3. Error Message Style Guide
\ No newline at end of file -- cgit v1.2.3