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

Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Philip Yarra <philip(at)utiba(dot)com>
Cc: Demetres Pantermalis <dpant(at)intracom(dot)gr>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Date: 2003-12-05 07:12:59
Message-ID: 20031205071259.GA6442@feivel.fam-meskes.de (view raw or flat)
Thread:
Lists: 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(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to

pgsql-interfaces by date

Next:From: Lee KindnessDate: 2003-12-05 09:19:51
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Previous:From: Philip YarraDate: 2003-12-04 22:44:19
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...

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