Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Lack of docs for libpq C Library


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, pgsql-docs(at)postgresql(dot)org
  • Subject: Re: Lack of docs for libpq C Library
  • Date: Thu, 31 Jan 2008 11:22:17 -0500
  • Message-id: <8892.1201796537@sss.pgh.pa.us> <text/plain>

Alvaro Herrera <alvherre(at)commandprompt(dot)com> 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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group