mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Add a nonlocalized version of the severity field to client error messages.
This has been requested a few times, but the use-case for it was never entirely clear. The reason for adding it now is that transmission of error reports from parallel workers fails when NLS is active, because pq_parse_errornotice() wrongly assumes that the existing severity field is nonlocalized. There are other ways we could have fixed that, but the other options were basically kluges, whereas this way provides something that's at least arguably a useful feature along with the bug fix. Per report from Jakob Egger. Back-patch into 9.6, because otherwise parallel query is essentially unusable in non-English locales. The problem exists in 9.5 as well, but we don't want to risk changing on-the-wire behavior in 9.5 (even though the possibility of new error fields is specifically called out in the protocol document). It may be sufficient to leave the issue unfixed in 9.5, given the very limited usefulness of pq_parse_errornotice in that version. Discussion: <A88E0006-13CB-49C6-95CC-1A77D717213C@eggerapps.at>
This commit is contained in:
@ -2767,6 +2767,22 @@ char *PQresultErrorField(const PGresult *res, int fieldcode);
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="libpq-pg-diag-severity-nonlocalized">
|
||||
<term><symbol>PG_DIAG_SEVERITY_NONLOCALIZED</></term>
|
||||
<listitem>
|
||||
<para>
|
||||
The severity; the field contents are <literal>ERROR</>,
|
||||
<literal>FATAL</>, or <literal>PANIC</> (in an error message),
|
||||
or <literal>WARNING</>, <literal>NOTICE</>, <literal>DEBUG</>,
|
||||
<literal>INFO</>, or <literal>LOG</> (in a notice message).
|
||||
This is identical to the <symbol>PG_DIAG_SEVERITY</> field except
|
||||
that the contents are never localized. This is present only in
|
||||
reports generated by <productname>PostgreSQL</> versions 9.6
|
||||
and later.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="libpq-pg-diag-sqlstate">
|
||||
<term>
|
||||
<symbol>PG_DIAG_SQLSTATE</>
|
||||
|
@ -4882,6 +4882,25 @@ message.
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<literal>V</>
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Severity: the field contents are
|
||||
<literal>ERROR</>, <literal>FATAL</>, or
|
||||
<literal>PANIC</> (in an error message), or
|
||||
<literal>WARNING</>, <literal>NOTICE</>, <literal>DEBUG</>,
|
||||
<literal>INFO</>, or <literal>LOG</> (in a notice message).
|
||||
This is identical to the <literal>S</> field except
|
||||
that the contents are never localized. This is present only in
|
||||
messages generated by <productname>PostgreSQL</> versions 9.6
|
||||
and later.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<literal>C</>
|
||||
|
Reference in New Issue
Block a user