Re: Support custom socket directory in pg_upgrade

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Support custom socket directory in pg_upgrade
Дата
Msg-id
24815.1543174602@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Support custom socket directory in pg_upgrade Daniel Gustafsson <daniel@yesql.se>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Daniel Gustafsson <daniel@yesql.se>
Re: Support custom socket directory in pg_upgrade Hironobu SUZUKI <hironobu@interdb.jp>
Re: Support custom socket directory in pg_upgrade Thomas Munro <thomas.munro@enterprisedb.com>
Re: Support custom socket directory in pg_upgrade Daniel Gustafsson <daniel@yesql.se>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Support custom socket directory in pg_upgrade Daniel Gustafsson <daniel@yesql.se>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Tom Lane <tgl@sss.pgh.pa.us>
Re: Support custom socket directory in pg_upgrade Daniel Gustafsson <daniel@yesql.se>
Re: Support custom socket directory in pg_upgrade Noah Misch <noah@leadboat.com>
Daniel Gustafsson  writes:
> [ pg_upgrade_sockdir-v3.patch ]

BTW, I notice that cfbot doesn't like this now that Thomas is running it
with -Werror:

option.c: In function ‘parseCommandLine’:
option.c:265:8: error: ignoring return value of ‘getcwd’, declared with attribute warn_unused_result [-Werror=unused-result]
  getcwd(default_sockdir, MAXPGPATH);
        ^
cc1: all warnings being treated as errors

Failing to check a syscall's result isn't per project style even if
the tools would let you get away with it.  Other places in that same
file do

		if (!getcwd(cwd, MAXPGPATH))
			pg_fatal("could not determine current directory\n");

			regards, tom lane

В списке pgsql-hackers по дате отправления
От: Laurenz Albe
Дата:
От: Stephen Frost
Дата:
FAQ