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

Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg

From: Eric Marsden <emarsden(at)mail(dot)dotcom(dot)fr>
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg
Date: 1998-08-12 14:29:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
>>>>> "HK" == Hannu Krosing <hannu(at)trust(dot)ee> 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.

This is my impression too: in postgresql-6.3.2/src/interfaces/libpgtcl/ 
there are C files which reference functions like PQconnectdb. However,
the documentation for libpgtcl states (this is from the top of

   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.

The documentation looks wrong, or perhaps it is talking about a
development version of libpgtcl? Should I report a documentation bug?

  HK> I've got the impression that there is currently a pure Tcl interface 
  HK> as well that some use with pgAccess on win32.

This is (Tcl interface at the
socket level).

Eric Marsden
emarsden @
It's elephants all the way down

In response to

pgsql-interfaces by date

Next:From: Tom LaneDate: 1998-08-12 14:33:15
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg
Previous:From: Eric MarsdenDate: 1998-08-12 14:04:07
Subject: Re: [INTERFACES] Re: thread-safe libpq and DBD::Pg

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group