database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Add support for multiple error messages from libpq, by simply appending them

Browse Source 
after each other (since we already add a newline on each, this makes them
multiline).

Previously a new error would just overwrite the old one, so for example any
error caused when trying to connect with SSL enabled would be overwritten
by the error message form the non-SSL connection when using sslmode=prefer.
This commit is contained in:
Magnus Hagander
2008-10-27 09:42:31 +00:00
parent 0fec77ae88
commit f3a0688ace
5 changed files with 54 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/sgml/libpq.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.265 2008/09/22 14:21:44 tgl Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.266 2008/10/27 09:42:31 mha Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
@ -1137,10 +1137,11 @@ PQconninfoOption *PQconninfoParse(const char *conninfo, char **errmsg);
Nearly all <application>libpq</> functions will set a message for
<function>PQerrorMessage</function> if they fail. Note that by
<application>libpq</application> convention, a nonempty
<function>PQerrorMessage</function> result will include a trailing
newline. The caller should not free the result directly. It will
be freed when the associated <structname>PGconn</> handle is passed
to <function>PQfinish</function>. The result string should not be
<function>PQerrorMessage</function> result can be multiple lines,
and will include a trailing newline. The caller should not free
the result directly. It will be freed when the associated
<structname>PGconn</> handle is passed to
<function>PQfinish</function>. The result string should not be
expected to remain the same across operations on the
<literal>PGconn</> structure.
</para>