Re: Non-portable shell code in pg_upgrade tap tests

Поиск
Список
Период
Сортировка
От Tels
Тема Re: Non-portable shell code in pg_upgrade tap tests
Дата
Msg-id c96303c04c360bbedaa04f90f515745b.squirrel@sm.webmail.pair.com
обсуждение исходный текст
Ответ на Re: Non-portable shell code in pg_upgrade tap tests  (Victor Wagner <vitus@wagner.pp.ru>)
Ответы Re: Non-portable shell code in pg_upgrade tap tests  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Moin,

On Fri, July 20, 2018 10:55 am, Victor Wagner wrote:
> On Fri, 20 Jul 2018 10:25:47 -0400
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> Victor Wagner <vitus@wagner.pp.ru> writes:
>> > I've discovered that in the branch REL_11_STABLE there is shell
>> > script src/bin/pg_upgrade/test.sh which doesn't work under Solaris
>> > 10. (it uses $(command) syntax with is not compatible with original
>> > Solaris /bin/sh)
>
>>
>> Please send a patch.  Most of us do not have access to old shells
>
> Here it goes. Previous letter was written before fixed tests were
> completed, because this old machine is slow.


+    *)    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?

Regards,

Tels



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

Предыдущее
От: Daniel Gustafsson
Дата:
Сообщение: Re: pread() and pwrite()
Следующее
От: "Tels"
Дата:
Сообщение: Re: Have an encrypted pgpass file