database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-21 16:02:15 +03:00
Code Activity

Improve libpq's handling of OOM during error message construction.

Browse Source 
Commit ffa2e4670 changed libpq so that multiple error reports
occurring during one operation (a connection attempt or query)
are accumulated in conn->errorMessage, where before new ones
usually replaced any prior error.  At least in theory, that makes
us more vulnerable to running out of memory for the errorMessage
buffer.  If it did happen, the user would be left with just an
empty-string error report, which is pretty unhelpful.

We can improve this by relying on pqexpbuffer.c's existing "broken
buffer" convention to track whether we've hit OOM for the current
operation's error string, and then substituting a constant "out of
memory" string in the small number of places where the errorMessage
is read out.

While at it, apply the same method to similar OOM cases in
pqInternalNotice and pqGetErrorNotice3.

Back-patch to v14 where ffa2e4670 came in.  In principle this could
go back further; but in view of the lack of field reports, the
hazard seems negligible in older branches.

Discussion: https://postgr.es/m/530153.1627425648@sss.pgh.pa.us
This commit is contained in:
Tom Lane
2021-07-29 13:33:31 -04:00
parent b35a67bc04
commit 514b4c11d2
4 changed files with 48 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
src/interfaces/libpq/fe-exec.c
View File

@ -191,7 +191,7 @@ PQmakeEmptyPGresult(PGconn *conn, ExecStatusType status)
/* non-error cases */
break;
default:
pqSetResultError(result, conn->errorMessage.data);
pqSetResultError(result, &conn->errorMessage);
break;
}
@ -662,14 +662,28 @@ pqResultStrdup(PGresult *res, const char *str)
* assign a new error message to a PGresult
*/
void
pqSetResultError(PGresult *res, const char *msg)
pqSetResultError(PGresult *res, PQExpBuffer errorMessage)
{
char *msg;
if (!res)
return;
if (msg && *msg)
res->errMsg = pqResultStrdup(res, msg);
/*
* We handle two OOM scenarios here. The errorMessage buffer might be
* marked "broken" due to having previously failed to allocate enough
* memory for the message, or it might be fine but pqResultStrdup fails
* and returns NULL. In either case, just make res->errMsg point directly
* at a constant "out of memory" string.
*/
if (!PQExpBufferBroken(errorMessage))
msg = pqResultStrdup(res, errorMessage->data);
else
res->errMsg = NULL;
msg = NULL;
if (msg)
res->errMsg = msg;
else
res->errMsg = libpq_gettext("out of memory\n");
}
/*
@ -852,19 +866,19 @@ pqInternalNotice(const PGNoticeHooks *hooks, const char *fmt,...)
/* XXX should provide a SQLSTATE too? */
/*
* Result text is always just the primary message + newline. If we can't
* allocate it, don't bother invoking the receiver.
* Result text is always just the primary message + newline. If we can't
* allocate it, substitute "out of memory", as in pqSetResultError.
*/
res->errMsg = (char *) pqResultAlloc(res, strlen(msgBuf) + 2, false);
if (res->errMsg)
{
sprintf(res->errMsg, "%s\n", msgBuf);
else
res->errMsg = libpq_gettext("out of memory\n");
/*
* Pass to receiver, then free it.
*/
res->noticeHooks.noticeRec(res->noticeHooks.noticeRecArg, res);
}
/*
* Pass to receiver, then free it.
*/
res->noticeHooks.noticeRec(res->noticeHooks.noticeRecArg, res);
PQclear(res);
}
@ -2122,7 +2136,7 @@ PQgetResult(PGconn *conn)
appendPQExpBuffer(&conn->errorMessage,
libpq_gettext("PGEventProc \"%s\" failed during PGEVT_RESULTCREATE event\n"),
res->events[i].name);
pqSetResultError(res, conn->errorMessage.data);
pqSetResultError(res, &conn->errorMessage);
res->resultStatus = PGRES_FATAL_ERROR;
break;
}