From: Michael Meskes <meskes@postgresql.org>
To: Philip Yarra <philip@utiba.com>
Cc: Demetres Pantermalis <dpant@intracom.gr>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
Date: Fri, 5 Dec 2003 08:12:59 +0100
Message-ID: <20031205071259.GA6442@feivel.fam-meskes.de> (raw)
In-Reply-To: <200312050944.19240.philip@utiba.com>
References: <NDBBLJPIEGAHHANHMMBBMENCDBAA.dpant@intracom.gr>
<200312050944.19240.philip@utiba.com>
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!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: meskes@postgresql.org, philip@utiba.com, dpant@intracom.gr
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres 7.4)...
In-Reply-To: <20031205071259.GA6442@feivel.fam-meskes.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox