Re: concurrent writes
От | Andreas Jung |
---|---|
Тема | Re: concurrent writes |
Дата | |
Msg-id | 1059475715.30414.30.camel@sentinel.sb.haufe.de обсуждение исходный текст |
Ответ на | Re: concurrent writes ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>) |
Ответы |
Re: concurrent writes
Re: concurrent writes |
Список | pgsql-general |
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
В списке pgsql-general по дате отправления: