| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | man pages |
| Date: | 2009-10-11 19:10:38 |
| Message-ID: | 20091011191038.GC14810@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Folks,
I'd like to see about creating man pages for the following:
- libpq
- SPI
- the built-in functions
These being what I've clicked through way too many web links to find
information about. If there are other things that should have man
pages, please mention same.
How would that be handled in our current doc build system? I'd really
appreciate any hints, tips or pointers on man page creation in our
current system :)
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-11 19:17:57 | Re: Is FOR UPDATE an optimization fence? |
| Previous Message | Tom Lane | 2009-10-11 18:00:19 | Re: Is FOR UPDATE an optimization fence? |