Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)... - Mailing list pgsql-interfaces

From Michael Meskes
Subject Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Date
Msg-id 20031205071259.GA6442@feivel.fam-meskes.de
Whole thread Raw
In response to Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...  (Philip Yarra <philip@utiba.com>)
List pgsql-interfaces
On Fri, Dec 05, 2003 at 09:44:19AM +1100, Philip Yarra wrote:
> The reason for this is below (I'm going from memory here, if I get this wrong 
> can someone correct me please?)
> ...
> I'm pretty sure what happens when you issue EXEC SQL SET CONNECTION is that it 
> sets the the default connection, so each of your threads would simply have 
> shuffled the default connection. Then when each thread attempts to EXEC SQL 
> they grab the same connection... whichever connection was made the default by 
> the last thread to issue EXEC SQL SET CONNECTION.

This is correct. SET CONNECTION just defines the default.

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


pgsql-interfaces by date:

Previous
From: Philip Yarra
Date:
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Next
From: Lee Kindness
Date:
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...