Message-ID: <c96303c04c360bbedaa04f90f515745b.squirrel@sm.webmail.pair.com>
In-Reply-To: <20180720175508.07776219@fafnir.local.vm>
References: <20180720153820.69e9ae6c@fafnir.local.vm>
    <17833.1532096747@sss.pgh.pa.us>
    <20180720175508.07776219@fafnir.local.vm>
Date: Fri, 20 Jul 2018 17:18:13 -0400
Subject: Re: Non-portable shell code in pg_upgrade tap tests
From: "Tels" <nospam-pg-abuse@bloodgate.com>
To: "Victor Wagner" <vitus@wagner.pp.ru>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>,
 "pgsql-hackers" <pgsql-hackers@postgresql.org>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Precedence: bulk

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