X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8BE20D1DA62 for ; Mon, 1 Dec 2003 22:37:10 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 06215-02 for ; Mon, 1 Dec 2003 18:36:44 -0400 (AST) Received: from candle.pha.pa.us (unknown [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 55E49D1D9E9 for ; Mon, 1 Dec 2003 18:36:40 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id hB1MaOT23226; Mon, 1 Dec 2003 17:36:24 -0500 (EST) From: Bruce Momjian Message-Id: <200312012236.hB1MaOT23226@candle.pha.pa.us> Subject: Re: quick ECPG doco change In-Reply-To: <200311191100.34246.philip@utiba.com> To: Philip Yarra Date: Mon, 1 Dec 2003 17:36:24 -0500 (EST) Cc: pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/3 X-Sequence-Number: 4612 Patch applied. Thanks. --------------------------------------------------------------------------- Philip Yarra wrote: > Hi, this doco patch is a quick one to add explicit mention of the need for the > AT clause in threaded ECPG applications. Does this sound okay? > > Bruce, yes, I do intend to contribute more than this, but at least this will > stop some confusion in the meantime. > > Regards, Philip Yarra. > > > Index: ecpg.sgml > =================================================================== > RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/ecpg.sgml,v > retrieving revision 1.54 > diff -c -r1.54 ecpg.sgml > *** ecpg.sgml 12 Nov 2003 22:47:47 -0000 1.54 > --- ecpg.sgml 18 Nov 2003 23:20:51 -0000 > *************** > *** 353,358 **** > --- 353,365 ---- > > This option is particularly suitable if the application needs to > use several connections in mixed order. > + > + > + > + If your application uses multiple threads of execution, they cannot > share a > + connection concurrently. You must either explicitly control access to > the connection > + (using mutexes) or use a connection for each thread. If each thread > uses its own connection, > + you will need to use the AT clause to specify which connection the > thread will use. > > > > > ------------------------------------------------------- > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073