[MASSMAIL]pgsql: Put back initialization of 'sslmode', to silence Coverity

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема [MASSMAIL]pgsql: Put back initialization of 'sslmode', to silence Coverity
Дата
Msg-id E1rw65i-0023yv-0N@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Put back initialization of 'sslmode', to silence Coverity

Coverity pointed out that the function checks for conn->sslmode !=
NULL, which implies that it might be NULL, but later we access it
without a NULL-check anyway. It doesn't know that it is in fact always
initialized earlier, in conninfo_add_defaults(), and hence the
NULL-check is not necessary. However, there is a lot of distance
between conninfo_add_defaults() and pqConnectOptions2(), so it's not
surprising that it doesn't see that. Put back the initialization code,
as it existed before commit 05fd30c0e7, to silence the warning.

In the long run, I'd like to refactor the libpq options handling and
initalization code. It seems silly to strdup() and copy strings, for
things like sslmode that have a limited set of possible values; it
should be an enum. But that's for another day.

Branch
------
master

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

Modified Files
--------------
src/interfaces/libpq/fe-connect.c | 6 ++++++
1 file changed, 6 insertions(+)


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

Предыдущее
От: Tomas Vondra
Дата:
Сообщение: pgsql: Fix unnecessary padding in incremental backups
Следующее
От: Peter Eisentraut
Дата:
Сообщение: [MASSMAIL]pgsql: Fix ALTER DOMAIN NOT NULL syntax