From: | Andreas Jung <andreas(dot)jung(at)haufe(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | concurrent writes |
Date: | 2003-07-29 10:33:06 |
Message-ID: | 1059474786.30414.26.camel@sentinel.sb.haufe.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
hi,
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 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. According to our postgres adminstrator, Postgres seems
to behave differently on Linux and Solaris. Any ideas on that?
Thanks,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Deepa K | 2003-07-29 10:40:12 | Can trigger procedures return value |
Previous Message | u15074 | 2003-07-29 10:24:18 | Re: View index question |
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-07-29 10:42:24 | Re: concurrent writes |
Previous Message | Shridhar Daithankar | 2003-07-29 08:57:44 | Re: Doubt w.r.t vacuum |