| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Fuhr <mike(at)fuhr(dot)org>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Config file for psql |
| Date: | 2006-02-28 19:48:31 |
| Message-ID: | 200602281948.k1SJmV526567@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Jim C. Nasby wrote:
> On Sat, Feb 18, 2006 at 02:49:08PM -0500, Tom Lane wrote:
> > Perhaps we should make a concerted effort to split the libpq docs into a
> > section "for programmers" vs one "for users", the latter part covering
> > the libpq behavior that is interesting to users of a libpq-based app.
> > .pgpass, pg_service, the environment vars, SSL behavior, maybe some
> > other things belong in the "for users" part.
>
> +1. Is there a docs TODO?
Added to TODO:
* Split out libpq pgpass and environment documentation sections
to make it easier for non-developers to find
Looking at the existing manual, how do we do this? Do we make separate
libpq-programming and a libpq-runtime sections?
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kulkarni | 2006-03-02 14:40:07 | Interactive comments for major versions |
| Previous Message | Bruce Momjian | 2006-02-25 04:29:25 | Re: Error correction to FAQ |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-28 19:49:31 | Re: character encoding in StartupMessage |
| Previous Message | Tom Lane | 2006-02-28 19:45:05 | Re: Zeroing damaged pages |