Re: [GENERAL] Management of Concurrent Clients

2006-02-26 Thread Tom Lane
Tino Wildenhain <[EMAIL PROTECTED]> writes: > Hanan Bentaleb schrieb: >> It has been reported to me that the main problem encountered with former >> postgresql versions is that when a process performs an update (of a >> record in any table), the whole database was locked > I wonder how they manage

Re: [GENERAL] Management of Concurrent Clients

2006-02-26 Thread Tino Wildenhain
Hanan Bentaleb schrieb: > Hi Tino, > > Thanks for your response! I did not provide more specific technical > details because I just came in to the project. So, I will try to provide > as much information as I can. > > Former versions of postgresql used in this project are postgresql > (starting a

Re: [GENERAL] Management of Concurrent Clients

2006-02-26 Thread Hanan Bentaleb
Wildenhain [mailto:[EMAIL PROTECTED] Sent: Sunday, February 26, 2006 12:54 PM To: Hanan Bentaleb Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Management of Concurrent Clients Hanan Bentaleb schrieb: > Hi all, > > > > I am working on an application that involves mul

Re: [GENERAL] Management of Concurrent Clients

2006-02-26 Thread Tino Wildenhain
Hanan Bentaleb schrieb: > Hi all, > > > > I am working on an application that involves multiple processes > accessing and updating different databases: tables are split into 3 > different databases that are accessed by 3 different processes. This > architectural decision was made in the past be

[GENERAL] Management of Concurrent Clients

2006-02-26 Thread Hanan Bentaleb
Hi all,   I am working on an application that involves multiple processes accessing and updating different databases: tables are split into 3 different databases that are accessed by 3 different processes. This architectural decision was made in the past because it has been noticed that f