Re: pg_migrator mention in documentation

On Sat, 6 Jun 2009, Bruce Momjian wrote:

> Having gotten no replies I assume we don't want to mention pg_migrator
> in the release notes or documentation, which is fine.

I know this project has resistance to putting URL links in the 
documentation.  One option I was thinking about was creating some 
dedicated pages on the Wiki to hold resource pages for things like 
pg_migrator, which are extremely useful but are still in flux at the time 
when the release goes out.

We could create a "Version Upgrade Resources" page, link to pg_migrator 
there, and include links to other related resources there too.  The 
documentation could just say "There are external tools available to 
upgrade between versions in some circumstances without a dump and reload, 
see http://wiki.postgresql.org/wiki/Version_Upgrade_Resources for more 
information".  That seems like a much more sustainable and permanent way 
to handle tools like this than directly linking to a project page for 
them, and gives capabilities like locking the page in order to prevent 
vandalism.

Two other areas which I'd like to see "packaged" formally for reference in 
the docs like this are a page listing replication tools and one listing 
postgresql.conf tuning resources.  Some of the known big problems with 
PosgreSQL have useful solutions, just not integrated ones yet, and we 
really should make it easier to popularize linking to those external tools 
in a controlled way.

I'd be happy to create proposed pages for each of these topics on the wiki 
if this idea seems reasonable to the community, there are rough articles 
there already for all three ideas I can pull from.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD