From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: concurrent writes |
Date: | 2003-07-29 17:01:32 |
Message-ID: | 20030729170132.GJ9011@libertyrms.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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 table. More detailed: every process
> opens its own connection, starts a transaction, updates *different* rows
> and then commits.
These two descriptions are not of the same thing. Different
processes cannot share the same transaction, unless they're using the
same connection.
> According to our postgres adminstrator, Postgres seems
> to behave differently on Linux and Solaris. Any ideas on that?
Differently how? Start up time for a connection is sure worse:
fork() on Solaris is slow as my dog with his foot in a bandage.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-07-29 17:02:44 | Re: concurrent writes |
Previous Message | Freddy Mnjvr | 2003-07-29 17:00:13 | how to get postgresql page size? |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2003-07-29 17:02:44 | Re: concurrent writes |
Previous Message | Andrew Dunstan | 2003-07-29 16:17:29 | Re: Make clean fails |