Re: [COMMITTERS] pgsql: Replace duplicate_oids with Perl implementation

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Replace duplicate_oids with Perl implementation
Date: 2013-11-13 02:01:33
Message-ID: 1384308093.23844.2.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sun, 2013-11-10 at 18:12 -0500, Tom Lane wrote:
> Perhaps, if we're worried about people keeping perl somewhere other
> than /usr/bin. However, the most likely reason for having a
> /usr/local/bin/perl or whatever is that it's a newer and shinier one
> than what's in /usr/bin. Since we're only interested in bog-standard
> perl, there's no real reason for us to want to pick up the local one.

After the Perl version of duplicate_oids was committed, some non-Windows
build farm member failed because it didn't have perl in /usr/bin. So
that appears to be a real issue.

> The particular application to this case might be: what makes
> you so sure env is in /bin?

I don't have a /bin/env, but the normal invocation is /usr/bin/env
anyway.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2013-11-13 02:02:41 Re: [COMMITTERS] pgsql: Replace duplicate_oids with Perl implementation
Previous Message Robert Haas 2013-11-12 16:31:06 Re: pgsql: Try again to make pg_isolation_regress work its build directory.

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-11-13 02:02:41 Re: [COMMITTERS] pgsql: Replace duplicate_oids with Perl implementation
Previous Message David Johnston 2013-11-13 01:49:00 Re: MVCC snapshot timing