Re: Non-portable shell code in pg_upgrade tap tests

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Non-portable shell code in pg_upgrade tap tests
Дата
Msg-id 4263.1532186967@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Non-portable shell code in pg_upgrade tap tests  ("Tels" <nospam-pg-abuse@bloodgate.com>)
Ответы Re: Non-portable shell code in pg_upgrade tap tests  (ilmari@ilmari.org (Dagfinn Ilmari Mannsåker))
Список pgsql-hackers
"Tels" <nospam-pg-abuse@bloodgate.com> writes:
> +    *)    if [ `find ${PGDATA} -type f ! -perm 640 | wc -l` -ne 0 ]; then

> Shouldn't ${PGDATA} in the above as argument to find be quoted, otherwise
> the shell would get confused if it contains spaces or other special
> characters?

Hmm.  Yeah, probably.  I don't think this script is meant to be run with
arbitrary values of PGDATA, but most of the other uses are quoted, so
for consistency's sake this should be too.

            regards, tom lane


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

Предыдущее
От: Marco van Eck
Дата:
Сообщение: Re: Have an encrypted pgpass file
Следующее
От: Brad DeJong
Дата:
Сообщение: grammar - src/backend/access/heap/README.tuplock