added a comment - - edited
Is there any work being done on this issue ? Postgresql cookbook seems to be unsable at the moment. Id really like to avoid having tons of execute resources as a workaround…using pg gem during chef run would be perfection…but at the moment impossible.
Basically the problem is simple. I don't know how Opscode are building the embedded ruby which comes with Omnibus install, but it looks like they're building them against not standard OS libraries. I had a go at installing the pg gem linking it against OS libs and all goes through just fine:
$ ruby --version
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
$ sudo gem install pg
Building native extensions. This could take a while...
Successfully installed pg-0.14.1
1 gem installed
Installing ri documentation for pg-0.14.1...
Installing RDoc documentation for pg-0.14.1...
The quintessential problem here is that the OpenSSL library Opscode's ruby is trying to link against when bulding 'pg' is different than the one that PostgreSQL was built with - this means that the omnibus ruby must be built against non-standard OS libraries ?? - meaning this is not built on actual versions of OS which he omnibus install.sh picker on http://www.opscode.com/chef/install/ is trying to suggest.
Would be awesome if the embedded ruby build was fixed with this regard. There is a few blockers which would be awesome if they were fixed.
Also one of the workarounds here is to use Opscode packages for chef-client. I would STRONGLY advise AGAINST that as the Opscode pacakge ship with ruby 1.8 - I guess I don't need to add more to this Interesting thing though is that Opscode package come with ruby 1.8 and omnibus with 1.9.3..