| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | emarsden(at)mail(dot)dotcom(dot)fr |
| Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
| Subject: | Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg |
| Date: | 1998-08-12 14:48:26 |
| Message-ID: | 4093.902933306@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Eric Marsden <emarsden(at)mail(dot)dotcom(dot)fr> writes:
>>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Brunton | 1998-08-12 19:51:33 | Back-end problems with Delphi and ODBCExpress |
| Previous Message | Tom Lane | 1998-08-12 14:33:15 | Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg |