From: Alan Hodgson
On Mon, 2020-03-02 at 18:23 -0500, Tom Lane wrote:
Kevin Brannen <
Centos 8 ships with 5.14 (IIRC).
I don't have an actual Centos 8 machine handy to disprove that,
but the info I have says that RHEL8/Centos 8 branched off from
Fedora 28, and F28 most definitely shipped
On Mon, 2020-03-02 at 18:23 -0500, Tom Lane wrote:
> Kevin Brannen writes:
> > On Centos 6.10, it ships with Perl 5.10.1, which is really ancient
> > tome.
>
> Well, yeah, because RHEL 6/Centos 6 are really ancient. That's
> whatI'd expect with a long-term-support distro that's nearly
> EOL.Repl
Kevin Brannen writes:
> On Centos 6.10, it ships with Perl 5.10.1, which is really ancient to
> me.
Well, yeah, because RHEL 6/Centos 6 are really ancient. That's what
I'd expect with a long-term-support distro that's nearly EOL.
Replacing its Perl version would go against the whole point of
an
From: Steven Lembark
>Funny thing is that both PG and Perl are easy enough to build from scratch and
>the centos compile of Perl at least is both ancient and horrid enough (5.00503
>compatibility, really?) that it's easier to just shell-script both builds and
>run it overnight.
>Q: How un-opt
On 2020-02-28 07:17:27 -0600, Steven Lembark wrote:
> RH and Debian distros are distriuted by heavy Python users who
> go out of their way to hamstring Perl at every step.
That's just complete bullshit, at least for Debian (I don't have current
experience with Redhat). The maintainer system makes
On 2020-02-28 07:13:12 -0600, Steven Lembark wrote:
> If you use the centos pre-compiled glob then you'll get their
> pre-compiled paths to their pre-compiled Perl which, among
> other things, is compiled with all optimization turned off,
> with 5.00503 compatibility turned *on*, and a host of ot
On Thu, 27 Feb 2020 15:07:29 -0500
Tom Lane wrote:
> You might be able to override that with LD_LIBRARY_PATH, but it's
> a pain, and it will certainly not work if your homebrew libperl
> isn't 100% ABI-compatible with the system one.
>
> Personally I'd build plperl against the Perl you want to u
On Thu, 27 Feb 2020 20:42:36 +
Kevin Brannen wrote:
> Thanks Tom, I can see your point. With the right change to
> LD_LIBRARY_PATH, I can make `ldd plperl.so` point to my Perl, but as
> you say, I'm probably playing with fire to expect it all to be 100%
> compatible between Perl 5.10.1 (Cento
> I can make Pg come up, initdb, that sort of stuff just fine. But we
> also use the Perl extension and we have references to Perl modules
> that are in *our* Perl and not the system one. Yes, we compile our
> own Perl like we provide our own Pg because Centos uses much older
> versions.
>
> The
From: Tom Lane
>Kevin Brannen writes:
>> The issue is that I've not been able to make Pg use our Perl (in
>> /opt/perl) instead of the system one (in /usr).
>
>plperl.so will typically have a more or less hard-coded path to libperl.so, eg
>
>$ ldd ...installdir.../lib/plperl.so
>linux-vd
Kevin Brannen writes:
> The issue is that I've not been able to make Pg use our Perl (in
> /opt/perl) instead of the system one (in /usr).
plperl.so will typically have a more or less hard-coded path to
libperl.so, eg
$ ldd ...installdir.../lib/plperl.so
linux-vdso.so.1 => (0x7ffc6
We're trying to upgrade our Pg 9.6 installs up to 12.2. In a break from
tradition where we grab source and compile our own, I've downloaded the
community RPMs for Centos 6 and installed them (they default into /usr/pgsql-12
it seems).
I can make Pg come up, initdb, that sort of stuff just fine.
12 matches
Mail list logo
