From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Subject: | install <install_path> doesn't work on HEAD |
Date: | 2018-06-05 13:38:00 |
Message-ID: | CAA4eK1+XuFzkPC21zzrKEdDraXUynB9C4hxAdMgiPsKFuucV4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On my win-7, I am facing $SUBJECT. I am consistently getting below error:
Copying build output files...Could not copy postgres.exe
at install.pl line 26.
On digging, I found that it started failing with commit 3a7cc727 (Don't
fall off the end of perl functions). It seems that we have added empty
'return' in all of the functions which seems to break one of the case:
lcopy("$conf\\$pf\\$pf.$ext", "$target\\$dir\\$pf.$ext")
|| croak "Could not copy $pf.$ext\n";
I think the return from lcopy implies 0 (or undef) which cause it to fail.
By reading couple of articles on net [1][2] related to this, it seems we
can't blindly return in all cases. On changing, the lcopy as below,
install appears to be working.
@@ -40,7 +40,7 @@ sub lcopy
copy($src, $target)
|| confess "Could not copy $src to $target\n";
- return;
+ return 1;
}
I have randomly check some of the other functions where this patch has
added 'return' and those seem to be fine.
Is it by any chance related Perl version or some other settings? If not,
then we should do something for it.
[1] - https://perlmaven.com/how-to-return-undef-from-a-function
[2] -
http://search.cpan.org/dist/Perl-Critic/lib/Perl/Critic/Policy/Subroutines/RequireFinalReturn.pm
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2018-06-05 13:39:24 | Re: why partition pruning doesn't work? |
Previous Message | Tomas Vondra | 2018-06-05 13:25:07 | Re: Spilling hashed SetOps and aggregates to disk |