postgresql documentation iimprovements - Mailing list pgsql-advocacy

From Merlin Moncure
Subject postgresql documentation iimprovements
Date
Msg-id 303E00EBDD07B943924382E153890E5434A902@cuthbert.rcsinc.local
Whole thread Raw
Responses Re: postgresql documentation iimprovements  (Neil Conway <neilc@samurai.com>)
Re: postgresql documentation iimprovements  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-advocacy
There was some discussion a little while back about improving the
documentation a little while back.  I have a couple of suggestions about
places where the documentation could be improved.

1. A 'best practices' section, either by command, or as a separate
section.

2. IMHO, The documentation for create rule is not clear and detailed
enough.  PHPfreaks.com has a very nice tutorial about this command and
how it could be used in a production database.  It is very important for
usage of this command to be clear, because only postgres has it, and
mastery of it gives you access to a very nifty feature, write back
views.

3. The technical discussion of transactions, MVCC, and locking and how
they interrelate could use some improvement.  Most especially, there
should be some practical examples for what happens during a transaction
conflict, lets say in a financial database.

Merlin


pgsql-advocacy by date:

Previous
From: Kevin Brown
Date:
Subject: Re: RedHat attitude
Next
From: Neil Conway
Date:
Subject: Re: postgresql documentation iimprovements