Return-Path: aoki
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA15254; Fri, 9 Jul 93 14:15:40 -0700
Message-Id: <9307092115.AA15254@postgres.Berkeley.EDU>
From: aoki@postgres.berkeley.edu (Paul M. Aoki)
Subject: Re: PQExec in Backend
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Fri, 9 Jul 1993 14:42:23 +22321159 (EDT) 
	     <9307091836.AA13097@postgres.Berkeley.EDU> 
Date: Fri, 09 Jul 93 14:20:10 -0700
Sender: aoki@postgres.Berkeley.EDU
X-Mts: smtp

dugan@torg.wpi.edu writes:
> Is it legal to issue PQExec() and all the other libpq
> calls in a dynamically loaded function in the backend?

in general, it's not kosher to link bits of libpq into the backend.
even if you don't run into name-space conflicts and conflicts between
libpq frontend stub routines and the corresponding backend routines,
it doesn't make much sense to be making libpq calls (which connect to 
the postmaster and fork off another backend server) from inside a backend.
--
  Paul M. Aoki  |  CS Div., Dept. of EECS, UCB  |  aoki@postgres.Berkeley.EDU
                |  Berkeley, CA 94720           |  ...!uunet!ucbvax!aoki