From: | Andreas Jung <andreas(dot)jung(at)haufe(dot)de> |
---|---|
To: | shridhar_daithankar(at)persistent(dot)co(dot)in |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: concurrent writes |
Date: | 2003-07-29 10:48:35 |
Message-ID: | 1059475715.30414.30.camel@sentinel.sb.haufe.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
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 need to write update/insert within the same time and within
> > the same transaction data in one table.
>
> What does it mean by same transaction data?
should read "update/insert within the same time and within the same
transaction 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?
>
> How it is different? It should be same, right?
Our experience was that the complete table has been locked (Solaris)
but row-level locking was working with Linux.
-aj
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-07-29 11:02:54 | Re: concurrent writes |
Previous Message | nolan | 2003-07-29 10:48:10 | Re: Can trigger procedures return value |
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-07-29 11:02:54 | Re: concurrent writes |
Previous Message | Shridhar Daithankar | 2003-07-29 10:42:24 | Re: concurrent writes |