[HACKERS] document and use SPI_result_code_string() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject [HACKERS] document and use SPI_result_code_string()
Date
Msg-id 559364af-6d67-4b44-4914-08571769f5a3@2ndquadrant.com
Whole thread Raw
Responses Re: [HACKERS] document and use SPI_result_code_string()  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
A lot of semi-internal code just prints out numeric SPI error codes,
which is not very helpful.  We already have an API function
SPI_result_code_string() to convert the codes to a string, so here is a
patch to make more use of that and also document it for external use.

Also included are two patches to clarify that some RI error handling
code that I encountered at the same time.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Tatsuro Yamada
Date:
Subject: [HACKERS] CLUSTER command progress monitor
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] Back-branch release notes up for review