Re: [DOCS] order of entries in admin docs

2008-05-08 Thread Ian Barwick 
2008/5/8 Peter Eisentraut <[EMAIL PROTECTED]>:
> Bruce Momjian wrote:
>> There isn't much additional text except a description of each item.
>
> That's the way it should be: Each parameter explains what it does.  There can
> be more extensive documentation about how they all fit together elsewhere.
>
> What I would like to see is getting rid of the sections the parameters are
> grouped in and put them all in alphabetical order.  I find the current
> arrangement completely unusable; nine times out of ten I cannot find the
> right section.  The topical grouping of the options would be the job of the
> more extensive documentation elsewhere I mentioned above.
>
> I think Postfix has arranged this nicely:
> http://www.postfix.org/documentation.html -- You have various sections
> explaining how to configure for various jobs, and one big list of all
> parameters explained.
>
> --
> Sent via pgsql-docs mailing list ([email protected])
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
>



-- 
http://sql-info.de/index.html

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] order of entries in admin docs

2008-05-08 Thread Ian Barwick 
(Whoops, apologies for the blank mail, I clicked on "send" by accident)

Ian Barwick

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] .backup files not needed?

2008-05-08 Thread Simon Riggs 
Just had questions from a replication user about why the .backup file is
described as "can ordinarily be ignored" and is considered optional by
recovery also even when pg_start_backup() was used.

If the file was created, it is necessary to use it in recovery, so
should never be ignored as the docs imply.

Can we remove the phrase ", and can ordinarily be ignored." ? from
doc/src/sgml/backup.sgml

  
To make use of the backup, you will need to keep around all the WAL
segment files generated during and after the file system backup.
To aid you in doing this, the pg_stop_backup function
creates a backup history file that is immediately
stored into the WAL archive area. This file is named after the first
WAL segment file that you need to have to make use of the backup.
For example, if the starting WAL file is
0001123455CD the backup history file will be
named something like
0001123455CD.007C9330.backup. (The second
part of the file name stands for an exact position within the WAL
file, and can ordinarily be ignored.) Once you have safely archived
the file system backup and the WAL segment files used during the
backup (as specified in the backup history file), all archived WAL
segments with names numerically less are no longer needed to recover
the file system backup and can be deleted. However, you should
consider keeping several backup sets to be absolutely certain that
you can recover your data.
   

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs