From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Igor Korot <ikorot01(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PQerrorMessage documentation |
Date: | 2017-05-05 01:57:55 |
Message-ID: | 84f3dbee-faae-6d47-4203-640336709dcf@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/3/17 21:23, Igor Korot wrote:
> Hi, ALL,
> [quote]
> Nearly all libpq functions will set a message for PQerrorMessage if
> they fail. Note that by libpq convention, a nonempty PQerrorMessage
> result can consist of multiple lines, and will include a trailing
> newline. The caller should not free the result directly. It will be
> freed when the associated PGconn handle is passed to PQfinish. The
> result string should not be expected to remain the same across
> operations on the PGconn structure.
> [/quote]
>
> Since there may be multiple errors, I presume that in this case the string
> will end with just \0, correct? It's not going to be \0\0 like with MSVC.
I don't know what you mean by \0\0 with MSVC, but it is correct that the
error message string will end with \0, like any C string.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Korot | 2017-05-05 03:51:36 | Re: PQerrorMessage documentation |
Previous Message | Igor Korot | 2017-05-04 23:30:46 | Link errors |