On Tue, Jul 29, 2003 at 12:33:06PM +0200, Andreas Jung wrote:
hi,
we are running Postgres 7.3.3 successfully on our portal sites
There's a nasty bug in 7.3.3 which is fixed in 7.3.4.
N processes need to write update/insert within the same time and within
the same transaction data in one
On Tue, Jul 29, 2003 at 01:07:57PM +0200, Andreas Jung wrote:
This problem appeard in 7.3.2 but it seems to have been fixed in 7.3.3.
Our administrator complained that there has not been a notice in the
CHANGELOG...so I am hestitating about choosing Postgres vs. Oracle :-)
I think your
On Tue, 2003-07-29 at 05:48, Andreas Jung wrote:
On Tue, 2003-07-29 at 12:42, Shridhar Daithankar wrote:
On 29 Jul 2003 at 12:33, Andreas Jung wrote:
we are running Postgres 7.3.3 successfully on our portal sites
under Solaris. For a new project we have the requirement that
N processes
If I understand your idea, and Postgres, this is like saying you want multiple backend processes, and definite, NO. As far as I know, one connection == 1 xaction.
Andreas Jung wrote:
hi,
we are running Postgres 7.3.3 successfully on our portal sites
under Solaris. For a new project we have the
