Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E31AE2E2FE8 for ; Thu, 31 Jan 2008 12:25:21 -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 55469-01-8 for ; Thu, 31 Jan 2008 12:25:08 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B8D502E3087 for ; Thu, 31 Jan 2008 12:22:20 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m0VGMHYs008893; Thu, 31 Jan 2008 11:22:17 -0500 (EST) To: Alvaro Herrera cc: Bruce Momjian , Pavel Golub , pgsql-docs@postgresql.org Subject: Re: Lack of docs for libpq C Library In-reply-to: <20080131152736.GG8602@alvh.no-ip.org> References: <434340074.20080131112041@gf.microolap.com> <200801311509.m0VF9Xp23007@momjian.us> <20080131152736.GG8602@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Thu, 31 Jan 2008 12:27:36 -0300" Date: Thu, 31 Jan 2008 11:22:17 -0500 Message-ID: <8892.1201796537@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/48 X-Sequence-Number: 4777 Alvaro Herrera writes: > 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). PQinitSSL *is* documented, though looking at the para immediately raises the question what the heck we are doing pointing to a random hp.com page for SSL documentation. PQsetClientEncoding seems to be documented in the wrong place. As for the expbuffer stuff, that is intentionally not considered part of libpq's exported API. If someone uses it, they get to keep both parts when it breaks. regards, tom lane