X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2B5CED1B1BE for ; Sat, 26 Jun 2004 22:31:15 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 51929-06 for ; Sun, 27 Jun 2004 01:31:13 +0000 (GMT) Received: from manage.24online (unknown [202.164.39.132]) by svr1.postgresql.org (Postfix) with ESMTP id 970E9D1B196 for ; Sat, 26 Jun 2004 22:30:54 -0300 (ADT) Received: from [192.168.200.2] ([172.16.0.141]) by manage.24online (8.9.3p2/8.9.3) with ESMTP id HAA19103 for ; Sun, 27 Jun 2004 07:03:00 +0530 Subject: Best approach to database design, in this case? From: Sanjay Arora Reply-To: skpobox@gawab.com To: pgsql-admin@postgresql.org Content-Type: text/plain Organization: Transcontinental Impex Pvt. Ltd. Message-Id: <1088299588.18791.81.camel@Sewak.Asr.Lan> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 27 Jun 2004 06:56:28 +0530 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/343 X-Sequence-Number: 14003 I am planning a vendor management module, which has to areas. One...A database located in DMZ, that will have user registration info and second in Green Segment of the Lan, which will have user information and correspondence, in addition to user registration. Now a user that comes in to register may already have a presence in the main database and may have come to the DMZ database from an invitation initiated from the main database. The DMZ DB is a subset of the main database, but contact/product information submitted by user overwrites that already existing. Now what should be the process? DMZ cannot contact the Green Database upon update, due to firewalling. So a periodic replication of records has to happen triggered by something. Or should I put the entire database in Green and use a SSH tunnel from the web-server in DMZ? What are the security approaches to this and their implications? Also, since the main database is heavily normalized and therefore querying (from internal processes...users from the net would have low registration & modification needs) would be much slower, I am planning along two lines. - Try to use materialized views. - Try Single Master-Multi Slave Replication and use something like pgpooling module announced in the announce mailing list today. What pg contrib/third party modules may I use and what are their reliability issues? Also, how does pg deal with NAS, especially the low cost ones built with EIDE or SATA drives? Anyone built one from low cost components? Looking for tips on all issues involved...especially using open source and low cost hardware as I am highly constrained by budgets. All/Any tips, warnings, help, URLs, pointers to further reading will be greatly appreciated. With best regards. Sanjay.