Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA12380; Wed, 29 Jan 92 19:59:55 -0800
Date: Wed, 29 Jan 92 19:59:55 -0800
Message-Id: <9201300359.AA12380@postgres.Berkeley.EDU>
From: George Hartzell <hartzell@genome.stanford.edu>
Subject: libpq philosophy, perl and Postgres...
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu


--- I mistakenly sent this to postarch ---

Ok, due to the lack of a deafening roar from the masses of people who
are polishing up the pgperl from the contrib section of the
postgres3.x release, I went ahead and did it myself.  I have a first
cut of something that works (it runs testlibpq after adding a
begin/end), but I need some philosophical help.

In, for instance, fe-pqexec.c there are a number of functions, some
are described as "SUPPORT ROUTINES", while others are "INTERFACE
ROUTINES".  Both of these are declared in the libpq-fe.h file, so in
that sense they are all accessible to people using libpq.  On the
other hand, none of them are mentioned in the ref. section on libpq.

What should I take as the definitive view on what libpq's public
interface is, the man page, the include file, the comments in the
source, or whatever I looks good to me?

While I'm at it, on page 83 of the reference (in libpq), the function
called PQnames should be PQpnames as far as I can tell.

Also, the ref section for monitor(1) describes a -A option, while the
source seems to use a -T.

And, on page 19, the query that generated the list of binary operators
from the system catalogs doesn't work as written.

g.

George Hartzell                                         voice: (415) 725-7421
Stanford Yeast Genome Project                           fax:   (415) 723-7016
Stanford School of Medicine, Rm S337   email: hartzell@sumex-aim.Stanford.EDU
Stanford, CA 94305-5120