search

EndPointCorp / end-point-blog

End Point Dev blog
https://www.endpointdev.com/blog/
17 stars 65 forks source link

Comments for Pl/Perl multiplicity issues with PostgreSQL - the Highlander restriction #688

Open phinjensen opened 7 years ago

phinjensen commented 7 years ago

Comments for https://www.endpointdev.com/blog/2012/09/plperl-multiplicity-postgres/ By Greg Sabino Mullane

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
phinjensen commented 7 years ago 
original author: Tim Bunce
date: 2012-09-04T15:34:52-04:00

A better solution is to recompile your Perl to enable multiplicity.

Ideally without also enabling threads, because enabling threads adds a small but significant performance cost.

In theory, one could even recompile Perl in-place and then restart Postgres, but I have never tried this out.

I'm pretty sure that won't work. Enabling multiplicity changes the binary compatibility.

phinjensen commented 7 years ago 
original author: Greg Sabino Mullane
date: 2012-09-04T22:20:41-04:00

Yes, I suppose it wouldn't work, as although #MULTIPLICITY would now be defined, and all the paths and files would be in the same place (presumably), one would need to at least 'make install' Postgres again so it would pick up the new macro inside of plperl.c. (Thank you for all your work on improving pl/perl, Tim! /aside)

phinjensen commented 7 years ago 
original author: Andrew Dunstan
date: 2012-09-05T19:28:14-04:00

I don't know why you would use a non-multiplicity-enabled perl if you're using plperl seriously.