public inbox for [email protected]  

help / color / mirror / Atom feed

From: Maciek Sakrejda <[email protected]>
To: [email protected]
Subject: Getting Started section
Date: Wed, 2 Mar 2016 00:07:35 -0800
Message-ID: <CAOtHd0DdB4QZy=VSw1fHm55NY1TEMxV6R4jAP9CkKhd17_GWBw@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

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

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: Getting Started section
  In-Reply-To: <CAOtHd0DdB4QZy=VSw1fHm55NY1TEMxV6R4jAP9CkKhd17_GWBw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox