Re: concurrent writes
От
Shridhar Daithankar
Тема
Re: concurrent writes
Дата
Msg-id
3F26A4EB.30385.541E6C8@localhost
Ответ на
Re: concurrent writes (Andreas Jung)
Список
Дерево обсуждения
concurrent writes Andreas Jung <andreas.jung@haufe.de>
Re: concurrent writes Andrew Sullivan <andrew@libertyrms.info>
Re: concurrent writes Dennis Gearon <gearond@cvc.net>
Re: concurrent writes "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
Re: concurrent writes Andreas Jung <andreas.jung@haufe.de>
Re: concurrent writes Ron Johnson <ron.l.johnson@cox.net>
Re: concurrent writes "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
Re: concurrent writes Andreas Jung <andreas.jung@haufe.de>
Re: concurrent writes Andrew Sullivan <andrew@libertyrms.info>
Re: concurrent writes Tom Lane <tgl@sss.pgh.pa.us>
Re: concurrent writes "Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>
Re: concurrent writes Andreas Jung <andreas.jung@haufe.de>
On 29 Jul 2003 at 13:07, Andreas Jung wrote: > On Tue, 2003-07-29 at 13:02, Shridhar Daithankar wrote: > > On 29 Jul 2003 at 12:48, Andreas Jung wrote: > > > Our experience was that the complete table has been locked (Solaris) > > > but row-level locking was working with Linux. > > > > Whoa!! That's something. How did you conclude it is locked. If you can produce > > some reproducible test case, this would be a big showstopper bug.. > > > > 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 :-) Even with 7.3.2, do you have a independently reproducible test case? It should help hackers to look into it. Bye Shridhar -- Matz's Law: A conclusion is the place where you got tired of thinking.
В списке pgsql-general по дате отправления
