<div class="moz-cite-prefix">On 06/12/2013 02:52 PM, Peter Geoghegan wrote:<br /></div><blockquote
cite="mid:CAM3SWZRquwEN02OEMqeZZp-E3TON+XtoGcXLs7cNOFaj8tAbPw@mail.gmail.com"type="cite"><pre wrap="">On Tue, Jun 11,
2013at 11:42 PM, Craig Ringer <a class="moz-txt-link-rfc2396E"
href="mailto:craig@2ndquadrant.com"><craig@2ndquadrant.com></a>wrote:
</pre><blockquote type="cite"><pre wrap="">Anyway, point being that PostgreSQL from Macports, Homebrew, and/or
EnterpriseDB's installer might be present ... and even in use.
</pre></blockquote><pre wrap="">
Perhaps you should direct those users towards <a class="moz-txt-link-freetext"
href="http://postgresapp.com">http://postgresapp.com</a>
</pre></blockquote><br /> Well, at that point they're usually already in a bit of a mess that they don't know how to
getthemselves out of. They're often *also* attempting to use Postgres.app, but struggling with issues with unix socket
directorydefaults, etc. The postgres.app docs do appear to offer some useful basic guidance for users on how to
uninstalllwhatever they might've installed.<br /><br /> None of this is hard if you have clue what you're doing.
Rebuildthe Pg gem against the right libpq by fixing your PATH so it finds the right pg_config, set host=/tmp, or set
host=localhost.Any of the three will work. Unfortunately most of these users seem to struggle with that, and their
approachto "it didn't work" appears to be "find another tool/tutorial and try that instead".<br /><br /> Sure, they're
notmy (or your) problem. I'd still like to see usability in this area improve if it's possible.<br /><br /> The
postgres.appdocumentation its self doesn't look quite right when it comes to Ruby, actually. For Ruby/Rails it says the
usershould use "gem install pg" but it doesn't tell them to set the PATH first, so they'll get whatever random
pg_configis on the PATH first, often Apple's elderly Pg with its different socket directory path, etc. Sure, they can
getaround that just by setting host: localhost, but it'd be nice to see that improved so it tells them how to build
theirPg gem against the correct libpq. Or, better, has Postgres.app automatically install it for them when they install
it.<br/><br /><br /><pre class="moz-signature" cols="72">-- Craig Ringer <a
class="moz-txt-link-freetext"href="http://www.2ndQuadrant.com/">http://www.2ndQuadrant.com/</a>PostgreSQL Development,
24x7Support, Training & Services</pre>