Re: 7.1 docs - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: 7.1 docs
Date
Msg-id Pine.LNX.4.30.0103241339310.2319-100000@peter.localdomain
Whole thread Raw
In response to Re: 7.1 docs  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
Responses Re: Re: 7.1 docs
List pgsql-hackers
Thomas Lockhart writes:

> I put in contacts.sgml a *long* time ago, thinking that something like
> it should be in the docs. But it was not complete enough to consider
> including at the time (now that I look, it only has my name ;), so it
> was only a placeholder for the future.

The "Resources" prefix section has contact info.  The rest is on the web
site.

> The ref/current_{date,time...}.sgml files are there because (a)
> functions should be documented, and (b) someone documented them. But we
> never documented enough functions to justify setting up an entire
> section of a manual to cover them. I think that these are more likely to
> be used in the future, but we do need additional pages written covering
> other functions.

All functions are documented (for appropriate values of "all") in the
User's Guide, chapter 4.  There was probably once the idea of setting up a
reference page set for the functions, but I don't know if this is
particularly better than what we have now.  In fact, I would argue it's
worse.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: AW: AW: Re: RELEASE STOPPER? nonportable int64 constant s in pg_crc.c
Next
From: Tom Lane
Date:
Subject: Re: AW: AW: Re: RELEASE STOPPER? nonportable int64 constant s in pg_crc.c