[MASSMAIL]pgsql: In psql, avoid leaking a PGresult after a query is cancelled.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема [MASSMAIL]pgsql: In psql, avoid leaking a PGresult after a query is cancelled.
Дата
Msg-id E1rtw6C-001Boa-8Y@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
In psql, avoid leaking a PGresult after a query is cancelled.

After a query cancel, the tail end of ExecQueryAndProcessResults
took care to clear any not-yet-read PGresults; but it forgot about
the one it has already read.  There would only be such a result
when handling a multi-command string made with "\;", so that you'd
have to cancel an earlier command in such a string to reach the
bug at all.  Even then, there would only be leakage of a single
PGresult per cancel, so it's not surprising nobody noticed this.
But a leak is a leak.

Noted while re-reviewing 90f517821, but this is independent of that:
it dates to 7844c9918.  Back-patch to v15 where that came in.

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a85e3ba1c9482dd04bec11588a5169a3430939af

Modified Files
--------------
src/bin/psql/common.c | 2 ++
1 file changed, 2 insertions(+)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: [MASSMAIL] pgsql: Further review for re-implementation of psql's FETCH_COUNT featu
Следующее
От: Michael Paquier
Дата:
Сообщение: [MASSMAIL] pgsql: injection_points: Fix race condition with local injection point