Re: Non-portable shell code in pg_upgrade tap tests

From: "Tels" <nospam-pg-abuse(at)bloodgate(dot)com>
To: "Victor Wagner" <vitus(at)wagner(dot)pp(dot)ru>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Non-portable shell code in pg_upgrade tap tests
Date: 2018-07-20 21:18:13
Message-ID: c96303c04c360bbedaa04f90f515745b.squirrel@sm.webmail.pair.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Victor Wagner <vitus(at)wagner(dot)pp(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tels 2018-07-20 21:22:24 Re: Have an encrypted pgpass file
Previous Message Daniel Gustafsson 2018-07-20 21:02:08 Re: pread() and pwrite()