MIME-Version: 1.0
Date: Wed, 2 Mar 2016 00:07:35 -0800
Message-ID: 
 <CAOtHd0DdB4QZy=VSw1fHm55NY1TEMxV6R4jAP9CkKhd17_GWBw@mail.gmail.com>
Subject: Getting Started section
From: Maciek Sakrejda <m.sakrejda@gmail.com>
To: pgsql-docs@postgresql.org
Content-Type: multipart/alternative; boundary=001a11409fcaf00368052d0c5f07
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

--001a11409fcaf00368052d0c5f07
Content-Type: text/plain; charset=UTF-8

I just spent some time helping a former colleague work out some basic setup
issues after he got stuck trying to follow the Getting Started section of
the manual [1] and almost gave up. For what it's worth, he's very
technical, but does not deal with Postgres setup regularly.

The problems he ran into are fairly trivial, but I can see how he was
frustrated: the article makes very few assumptions about your environment
(which is great), but as a result is really vague and full of evasive
suggestions to "contact your administrator" if something is not working
(not great).

All I had to do (on Ubunutu) was run `sudo -u postgres createuser -s
$(whoami)`, and then omit the hostname (connecting to postgres:///maciek)
to use socket connections so I could take advantage of peer authentication
to avoid having to specify my password everywhere. The same thing worked
for him (on Debian, I believe).

Obviously this is not a solution for everyone, but I think packaging is
more common and more standardized these days, and administrators who may
have set up Postgres for you and can help you get started are less common.

I'm not sure how to address his frustrations, and balance that with
avoiding too many assumptions about users' environments, but it seems many
successful tools these days have explicit, platform-specific sections of
their setup to ensure that users can get started quickly and painlessly.
Could the Getting Started guide be improved here? Thoughts?

Thanks,
Maciek

[1]: http://www.postgresql.org/docs/9.4/static/tutorial-createdb.html

--001a11409fcaf00368052d0c5f07
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I just spent some time helping a former colleague wor=
k out some basic setup issues after he got stuck trying to follow the Getti=
ng Started section of the manual [1] and almost gave up. For what it&#39;s =
worth, he&#39;s very technical, but does not deal with Postgres setup regul=
arly.</div><div><br></div><div>The problems he ran into are fairly trivial,=
 but I can see how he was frustrated: the article makes very few assumption=
s about your environment (which is great), but as a result is really vague =
and full of evasive suggestions to &quot;contact your administrator&quot; i=
f something is not working (not great).</div><div><br></div><div>All I had =
to do (on Ubunutu) was run `sudo -u postgres createuser -s $(whoami)`, and =
then omit the hostname (connecting to postgres:///maciek) to use socket con=
nections so I could take advantage of peer authentication to avoid having t=
o specify my password everywhere. The same thing worked for him (on Debian,=
 I believe).</div><div><br></div><div>Obviously this is not a solution for =
everyone, but I think packaging is more common and more standardized these =
days, and administrators who may have set up Postgres for you and can help =
you get started are less common.</div><div><br></div><div>I&#39;m not sure =
how to address his frustrations, and balance that with avoiding too many as=
sumptions about users&#39; environments, but it seems many successful tools=
 these days have explicit, platform-specific sections of their setup to ens=
ure that users can get started quickly and painlessly. Could the Getting St=
arted guide be improved here? Thoughts?</div><div><br></div><div>Thanks,</d=
iv><div>Maciek</div><div><br></div><div>[1]:=C2=A0<a href=3D"http://www.pos=
tgresql.org/docs/9.4/static/tutorial-createdb.html" target=3D"_blank">http:=
//www.postgresql.org/docs/9.4/static/tutorial-createdb.html</a></div><div><=
br></div><div><br></div></div>

--001a11409fcaf00368052d0c5f07--