DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
 h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=beVCwcEbpsvJb81h/2NKNGUs3MVoES3QS6XkMcJHbLH+dJFz0yBCNkTt7udHHB3WGLUhqfC9fLxdF4MRDMzbu33LWA+o5qWMLVDYHoeUY3Xx5pD3hKZOT+BUfiwEc0P6YuMGM9v3knW8Hlcj3RkKKUI41MRxowhxolGiW9g+En0=;
References: 
 <CA+94MuaJTHjqrffz-wiuyF56r=nGG1GC96CTG_Gou5j7Vno_YA@mail.gmail.com> 
Message-ID: <1389108760.77027.YahooMailNeo@web122301.mail.ne1.yahoo.com>
Date: Tue, 7 Jan 2014 07:32:40 -0800 (PST)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: pgAmin III 1.18.0 docs.
To: Barry Gysbers <barrygysbers@gmail.com>,
 "pgsql-docs@postgresql.org" <pgsql-docs@postgresql.org>
In-Reply-To: 
 <CA+94MuaJTHjqrffz-wiuyF56r=nGG1GC96CTG_Gou5j7Vno_YA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

Barry Gysbers <barrygysbers@gmail.com> wrote:

> I am an experienced database user/programmer.=A0 I am absolutely
> brand new to PostgreSQL.=A0 I just downloaded 9.3.0 on 2013Oct01
> and am finally getting over my reluctance to learn a new system
> and taking a look at it.=A0 The file was
> postgresql-9.3.0-1-windows.exe

Welcome to the PostgreSQL world!=A0 One of the first things you might
want to check out is the page regarding versioning:

http://www.postgresql.org/support/versioning/

In PostgreSQL we are very conservative about what goes into a minor
release (where the numbers don't change to the left of the second
dot); only fixes for security vulnerabilities and serious bugs are
considered for a minor release, and conversion of the database is
never required.=A0 This is so that users can upgrade with minimal
risk that anything will be broken by applying the bug fixes.=A0 With
9.3.0 you are missing three months worth of bug fixes.=A0 I recommend
that you grab the latest 9.3 minor release, to avoid finding all
the "dot zero" bugs which others have already found and fixed.=A0 It
generally pays to stay fairly up-to-date as new minor releases
become available.

> and this email refers to the documentation that came with that
> package.
>=20
> I started reading the documentation today for pgAdmin III 1.18.0
> as it seems that I must use pgAdmin III in order to get any work
> done.

While some packagers may include pgAdmin with the PostgreSQL
distribution, it really is a separate product.=A0 The interface which
is included with PostgreSQL is psql, a command-line tool which is
very flexible and helpful.=A0 It is probably worth trying that out,
just so you are familiar with some of what it can do.

> I have only read about a dozen pages before becoming
> overloaded.=A0 With the exception of changing the passworld, I have
> no idea what I read means, nor the significance of any of it.=A0 I
> would think that it would be more helpful to either explain what
> you are expected to already know before being able to use the
> documentation, or, (more skillfully), put links that explain what
> each technical term means, and/or what relevance/consequence each
> decision you make has.

You may want to start with the documentation for the database
product itself before dealing with the docs for a GUI tool to work
with the database; that might give the background which would allow
the tool's docs to make more sense.

http://www.postgresql.org/docs/9.3/static/index.html

Of course, that doesn't mean that the pgAdmin docs couldn't be
improved; I'm just suggesting it as a way to get the information
you want from existing docs.

> Mostly, I just wanted to point out that there are an absolutely
> incredible number of typos on the very few pages that I have
> slogged through so far.

> I would be happy to provide at least some editing services as my
> contribution to the project, (being absolutely ignorant of
> anything actually useful), provided there was some guarantee that
> they would actually be implemented or otherwise used.

I don't know about an absolute guarantee, but I would be surprised
if the committers for pgAdmin would ignore corrections.

> I would have to be told exactly how to go about making changes in
> a way that would be considered useful.

Your best bet would be to download the source code from here:

http://www.pgadmin.org/development/git.php

... and submit context diff patches to the pgadmin-hackers list.
The pgsql-* lists are not really the right place for discussion or
submissions for pgAdmin.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs