| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | document and use SPI_result_code_string() |
| Date: | 2017-08-31 02:23:01 |
| Message-ID: | 559364af-6d67-4b44-4914-08571769f5a3@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Move-SPI-error-reporting-out-of-ri_ReportViolation.patch | text/plain | 3.3 KB |
| 0002-Add-attribute-noreturn.patch | text/plain | 829 bytes |
| 0003-Document-and-use-SPI_result_code_string.patch | text/plain | 6.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2017-08-31 02:53:45 | Re: Back-branch release notes up for review |
| Previous Message | Tatsuro Yamada | 2017-08-31 02:12:02 | CLUSTER command progress monitor |