Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7C4672E0239 for ; Thu, 31 Jan 2008 11:31:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 16324-01-4 for ; Thu, 31 Jan 2008 11:31:18 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 2611B2E3052 for ; Thu, 31 Jan 2008 11:27:49 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-113-152.bk8-dsl.surnet.cl [200.126.113.152]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m0VFRotx026904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Jan 2008 07:27:53 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 2489647BEA; Thu, 31 Jan 2008 12:27:36 -0300 (CLST) Date: Thu, 31 Jan 2008 12:27:36 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Pavel Golub , pgsql-docs@postgresql.org Subject: Re: Lack of docs for libpq C Library Message-ID: <20080131152736.GG8602@alvh.no-ip.org> References: <434340074.20080131112041@gf.microolap.com> <200801311509.m0VF9Xp23007@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200801311509.m0VF9Xp23007@momjian.us> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 31 Jan 2008 07:27:53 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/46 X-Sequence-Number: 4775 Bruce Momjian wrote: > Pavel Golub wrote: > > Hello, pgsql-docs. > > > > I noticed that some exported functions are not documented in the > > Chapter 30. However, there are some info about them in other chapters, > > e.g. PQclientEncoding using is described in chapter 22.2.3 "Automatic > > Character Set Conversion Between Server and Client". > > Though they are exported, the are more for internal use, e.g. psql, > rather than something we want people using --- they can change from > release to release. I disagree. I think PQinitSSL is meant to be called from the application, for example. Same with PQsetClientEncoding. And the PQExpBuffer stuff is all very useful, and years ago when I wrote an app to use it it annoyed me that there were no docs on it. (Back then, I didn't realize I could have complained about it or written the docs myself). > --------------------------------------------------------------------------- > > > > > > This is the list of exported functions without docs: > > ================ > > PQclientEncoding > > PQsetClientEncoding > > PQconninfoFree > > PQdsplen > > PQenv2encoding > > PQinitSSL > > PQmblen > > PQregisterThreadLock > > appendPQExpBuffer > > appendPQExpBufferChar > > appendPQExpBufferStr > > createPQExpBuffer > > destroyPQExpBuffer > > enlargePQExpBuffer > > initPQExpBuffer > > appendBinaryPQExpBuffer > > pg_char_to_encoding > > pg_encoding_to_char > > pg_utf_mblen > > pg_valid_server_encoding > > pgresStatus > > pqsignal > > printfPQExpBuffer > > resetPQExpBuffer > > termPQExpBuffer -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.