On 8/26/08, Andrew Sullivan <ajs at crankycanuck.ca> wrote:
>
>  I know it sucks to get "RTFM", but actually the Slony manual, while
>  verbose, is fairly complete.  Unfortunately, you need to read it in
>  order to operate the software.



It does not suck to get an RTFM if the M is written in an intelligible
manner. The Slony documentation is horribly incomplete for people who
are new to the system. The purpose of documentation is not to have
people sit around for a month to figure out what works where how.

A simple scenario -- typical one! -- would go a long way in making
Slony docs useful. I have been saying this throughout this thread:

1. Install Slony (Done. This was okay).

2. Install new instance of PG. Take a typical PG install. Include
thoughts on installing in a NEW DIRECTORY so that it doesn't conflict
with existing PG.

3. Do the master/slave stuff. I find it hard to believe that there is
NO default situation. There has to be a default config, right? Even if
the performance is bad or whatever, it at least serves as a starting
point. This would illustrate whatever is needed for setting up
"clusters" (a fun feast of reading) and whatnot.

4. When the new install is working, how to switch between new and old.

5. How to delete old.

The "concepts" page tells me nothing. I have read it, and the ENTIRE
slony documentation, plus some google pages here and there. Not a
single thing that explains how to do stuff.

I am not interested in being a Slony expert or a fabulous DBA. I just
want something that does the job of letting me upgrade a DB. (I am not
looking for regular replication, but I was forwarded from the
PG-GENERAL list to come here and ask how to use Slony to perform the
anal experience that is the PG upgrade. I am not impressed so far!)

Thanks for sharing your thoughts anyway. I'd appreciate some specific
help from others.