Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org
	(8.8.8/8.7.5) with ESMTP id KAA27020 for
	<pgsql-interfaces@postgreSQL.org>;
	Wed, 12 Aug 1998 10:48:51 -0400 (EDT)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA04095;
	Wed, 12 Aug 1998 10:48:26 -0400 (EDT)
To: emarsden@mail.dotcom.fr
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg 
In-reply-to: Your message of 12 Aug 1998 16:29:14 +0200
	<m23eb2e0jp.fsf@cook.onecert.fr>
Date: Wed, 12 Aug 1998 10:48:26 -0400
Message-ID: <4093.902933306@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Eric Marsden <emarsden@mail.dotcom.fr> writes:
>>>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
TL> The present libpgtcl is NOT pure Tcl --- it is a C-coded Tcl
TL> extension, besides which it is layered on top of libpq.

> the documentation for libpgtcl states (this is from the top of
> postgresql-6.3.2/doc/src/sgml/libpgtcl.sgml)

>    pgtcl is a tcl package for front-end programs to interface with
>    <ProductName>Postgres</ProductName> backends. pgtcl does not use
>    the libpq library but communicates to the backend directly via the
>    frontend-backend protocol. Thus, it is more efficient than previous
>    postgres->tcl bindings which are layered on top of libpq. In
>    addition, pgtcl can handle multiple backend connections from a
>    single frontend application.

Yeah, that paragraph is all wet --- perhaps there once was a libpgtcl
written that way, but the current distribution certainly is not it.
I took that para out of the CVS sources some time ago.

			regards, tom lane