Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4D0E4475E18 for ; Thu, 9 Jan 2003 16:33:38 -0500 (EST) Received: from com.ith.tur.cu (com.ith.tur.cu [212.44.111.34]) by postgresql.org (Postfix) with ESMTP id 1C40E475CB4 for ; Thu, 9 Jan 2003 16:33:35 -0500 (EST) Received: from nsoft by com.ith.tur.cu with SMTP (MDaemon.PRO.v6.0.7.R) for ; Thu, 09 Jan 2003 16:35:14 -0500 Message-ID: <00d701c2b840$1dbedaa0$8a24a8c0@nsoft> Reply-To: "enediel" From: "enediel" To: "postgresql" Subject: Fw: Fw: Fw: postgresql in cluster of servers Date: Thu, 9 Jan 2003 16:35:01 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Return-Path: enediel@com.ith.tur.cu X-MDaemon-Deliver-To: pgsql-performance@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/70 X-Sequence-Number: 717 Thanks for the answer scott.marlowe I'm agree with you about the limit of the I/O operations with this configuration. I'm just looking for a fault tolerance configuration in the databases server, considering a very large databases, and a lot of users accesing to them. I'll accept with pleasure any suggestions about this topic. Greetings Enediel Linux user 300141 Happy who can penetrate the secret causes of the things ĦUse Linux!