From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
---|---|
To: | Daniel Schuchardt <daniel_schuchardt(at)web(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: 2 connections 1 transaction |
Date: | 2003-07-17 14:57:58 |
Message-ID: | 3F16B976.80306@openratings.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The short answer is - there is no way you can do it.
Different connections in postgres (and in every other DB engine I heard
of) can never share the same transaction.
As far as I can see, the only way to do what you want is to rethink your
architechture so that the clients never talk directly to the database,
and always go through the app server... or, the other way around - get
rid of the app server, and just have every client go to the database
directly. You can' thave it both ways.
Dima
Daniel Schuchardt wrote:
> Hi @ all,
>
> Our software consists of a Client-Side App and a Application Server.
> Every client owns a direct connection to the PSql-Server and for every
> Client the Application-Server also creates a connection to the
> PSql-Server. The problem is that it is nescesary that the Client and
> the Application-Server are in the same transaction. But how say
> connection x to be in the same transaction like connection y?
>
> Thanks for help,
>
> Daniel
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Terence Chang | 2003-07-17 15:11:48 | Re: Where is the physical files of database that I just |
Previous Message | scott.marlowe | 2003-07-17 14:53:06 | Re: Strange behaviour of Postgresql (Postgresql 7.3.3 |