From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/plpgsql-errors-and-messages.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/plpgsql-errors-and-messages.html') diff --git a/doc/src/sgml/html/plpgsql-errors-and-messages.html b/doc/src/sgml/html/plpgsql-errors-and-messages.html index 57c7030..21b7e73 100644 --- a/doc/src/sgml/html/plpgsql-errors-and-messages.html +++ b/doc/src/sgml/html/plpgsql-errors-and-messages.html @@ -1,5 +1,5 @@ -43.9. Errors and Messages
43.9. Errors and Messages
Prev UpChapter 43. PL/pgSQL — SQL Procedural LanguageHome Next

43.9. Errors and Messages

43.9.1. Reporting Errors and Messages
43.9.2. Checking Assertions

43.9.1. Reporting Errors and Messages

+43.9. Errors and Messages

43.9. Errors and Messages
Prev UpChapter 43. PL/pgSQL — SQL Procedural LanguageHome Next

43.9. Errors and Messages

43.9.1. Reporting Errors and Messages
43.9.2. Checking Assertions

43.9.1. Reporting Errors and Messages

Use the RAISE statement to report messages and raise errors. @@ -145,4 +145,4 @@ ASSERT condition [ASSERT is meant for detecting program bugs, not for reporting ordinary error conditions. Use the RAISE statement, described above, for that. -

Prev Up Next
43.8. Transaction Management Home 43.10. Trigger Functions
\ No newline at end of file +

Prev Up Next
43.8. Transaction Management Home 43.10. Trigger Functions
\ No newline at end of file -- cgit v1.2.3