pgsql: Fix memory leak coming from simple lists built in reindexdb

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема pgsql: Fix memory leak coming from simple lists built in reindexdb
Дата
Msg-id E1hsHNg-0006Ud-Sb@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Fix memory leak coming from simple lists built in reindexdb

When building a list of relations for a parallel processing of a schema
or a database (or just a single-entry list for the non-parallel case
with the database name), the list is allocated and built on-the-fly for
each database processed, leaking after one database-level reindex is
done.  This accumulates leaks when processing all databases, and could
become a visible issue with thousands of relations.

This is fixed by introducing a new routine in simple_list.c to free all
the elements in a simple list made of strings or OIDs.  The header of
the list may be using a variable declaration or an allocated pointer,
so we don't have a routine to free this part to keep the interface
simple.

Per report from coverity for an issue introduced by 5ab892c, and
valgrind complains about the leak as well.  The idea to introduce a new
routine in simple_list.c is from Tom Lane.

Author: Michael Paquier
Reviewed-by: Tom Lane

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/04cf0bfc90dfae89a794d2bdd88fe3b8e313798e

Modified Files
--------------
src/bin/scripts/reindexdb.c        |  6 ++++++
src/fe_utils/simple_list.c         | 38 ++++++++++++++++++++++++++++++++++++++
src/include/fe_utils/simple_list.h |  2 ++
3 files changed, 46 insertions(+)


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Fix busted logic for parallel lock grouping in TopoSort().
Следующее
От: Tomas Vondra
Дата:
Сообщение: pgsql: Don't build extended statistics on inheritance trees