[chef] Re: Re: Re: Re: [COOK-1406] Roadmap for chef-omnibus + postgresql?

[Torben Knerr < >]

On Tue, Sep 25, 2012 at 7:50 PM, Lamont Granquist < " target="_blank"> > wrote:

On 9/25/12 6:40 AM, Jay Levitt wrote:

The better solution is probably to compile the pg libraries from source,
making sure to get -I and -L flags right to pick up the omnibus openssl and
install those in the omnibus directory. Do that at compile time after
installing build-essentials, but before calling chef_gem.

Which cookbook should this go in?  I could take a crack at it, though anything that slows the first converge makes me sad, and Postgres compiles take two minutes on a fast machine (though that's the whole server; client-only may be faster).

It should be a postgresql cookbook recipe to install the client from source.

To speed this up, it could be compiled once, installed into a different directory outside of /opt/opscode (but build with the -I and -L flags pointed at the openssl in omnibus) then with chef_gem with appropriate options to point at it, and you can fpm that libpg up into an rpm/deb and install it from an internal mirror or from S3 or whatever.  You could probably even try to just fpm it up from inside of /opt/opscode, but I don't know how messy that would be. Same goes for the pg gem itself as well (and if you can just point fpm at the omnibus ruby, that might be trivial to package the pg gem)

Hi Jay,

did you actually come to fixing the postgres cookbook for omnibus installs?

Need it too, but don't want to look for further workaround if it has been done already.

Cheers,

Torben