Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2463537C0C7 for ; Mon, 6 Oct 2008 14:54:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 48079-10 for ; Mon, 6 Oct 2008 14:54:29 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.186]) by postgresql.org (Postfix) with ESMTP id B510337BACB for ; Mon, 6 Oct 2008 14:54:28 -0300 (ADT) Received: by ti-out-0910.google.com with SMTP id y8so1495979tia.5 for ; Mon, 06 Oct 2008 10:54:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=k8xV1SorYi8UIJb2OAymFGv33QdmpNgaESezCeJ/DGE=; b=nL9Yu6a6qzIV22DGDKFYNwQr6U5T7It6NQYIOR6kcH/I/nM9sDMLpMOWTNSiKYywVz 6ZsoFiexAXRnfR+7d++Y+R8Vq2UO/z0yenu+H70cyIxBSCh7pt0rTa6yHPlEGbgEYPiG KuOQblojwTIHLcg8DZPj8yWoqkQGd+njTlZxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=AorLqkVg9vjAxvOc8zBEK3kISLNp6TQPCByViZjHDRgtQKz7xwkej5g3K9D5DGAVja OJ9ktrEdCZOJCh/zgcZu+SlSomQSwFysvHDwoEAIzuiaNkYLcsGkjNQOlHBbN10UUpn2 1qgTVUaPpc5OjtnyBolxgKsoRAn9oAG2rfNnI= Received: by 10.110.15.9 with SMTP id 9mr6635966tio.12.1223315661215; Mon, 06 Oct 2008 10:54:21 -0700 (PDT) Received: by 10.110.52.16 with HTTP; Mon, 6 Oct 2008 10:54:21 -0700 (PDT) Message-ID: Date: Mon, 6 Oct 2008 21:54:21 +0400 From: "Mohammed Rashid" To: "Scott Marlowe" Subject: Re: Postgres database as a client/server architecture Cc: Rich , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8fb205ea0810060800t6a14d70bo85bc55dd8db32914@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/32 X-Sequence-Number: 30488 Hi All, I think there is some confusion regarding this. I want postgres to be installed at two different PCs.Then the data from each postgres should be automatically updated to the third PC which we call server. This process should be automatic. It should also take care of network disconnection between client and server. After establishment of network connections the remaining data should be automatically updated to the server. It is bit different from the mirroring of databases, but the concept is same. I just want to ask whether the Postgres database supports this or not? Or I have to write an application to do so. I am hoping to read soon from you. Thanks for your response. Regards, Rashid On Mon, Oct 6, 2008 at 7:08 PM, Scott Marlowe wrote: > On Mon, Oct 6, 2008 at 9:00 AM, Rich wrote: >> On Mon, Oct 6, 2008 at 10:08 AM, Scott Marlowe wrote: >>> On Mon, Oct 6, 2008 at 12:23 AM, Mohammed Rashid wrote: >>>> Hi All, >>>> >>>> I have use the Postgres database as a client/server architecture. >>>> I mean I want to run the clients on different PCs and want that all >>>> the transactions should get automatically updated in the server. >>>> It should also take care of network disconnections and update the >>>> server after network connections automatically. >>> >>> PostgreSQL already is a client server architecture. However, it >>> sounds like what you're actually looking for is some kind of client AS >>> server method where the clients can operate independently then update >>> the database at some later date. >>> >>> PostgreSQL has no facilities to do this on its own. >> >> Actually it does have those facilities to do such an architecture. >> Its callled psql. Postgresql's verison of sql. just write sql >> statements to update, delete or add records accordingly. You can do >> this using a web interface, another client db like access or paradox. >> There are tons of ways to do it. you can use an odbc interface. So >> postgress does come with everything you need. > > Not if what the OP wants is the lotus notes type functionality where > things are updated on the client, and at some later date updated on > the main server and all data inconsistencies are automagically taken > care of. > > OTOH, if all the OP wanted was to just have plain old client - server > architecture, yeah, that's built right in to psql / libpq... >