| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Document and use SPI_result_code_string() |
| Date: | 2017-10-05 02:15:35 |
| Message-ID: | E1dzvhH-0006GW-FK@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Document and use SPI_result_code_string()
A lot of semi-internal code just prints out numeric SPI error codes,
which is not very helpful. We already have an API function to convert
the codes to a string, so let's make more use of that.
Reviewed-by: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/036166f26e00ab3286ef29a6519525d6291fdfd7
Modified Files
--------------
contrib/spi/refint.c | 6 ++---
contrib/spi/timetravel.c | 2 +-
doc/src/sgml/spi.sgml | 53 +++++++++++++++++++++++++++++++++++++
src/backend/utils/adt/ri_triggers.c | 10 +++----
src/test/regress/regress.c | 2 +-
5 files changed, 63 insertions(+), 10 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-05 02:17:09 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Wood, Dan | 2017-10-05 01:39:52 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |