Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 067D837BD27 for ; Mon, 6 Oct 2008 12:08:51 -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 10077-01-3 for ; Mon, 6 Oct 2008 12:08:37 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by postgresql.org (Postfix) with ESMTP id BAE2A37C9F7 for ; Mon, 6 Oct 2008 12:08:34 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 25so2781213wfc.28 for ; Mon, 06 Oct 2008 08:08:32 -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=JOvMKZtD09By8qYo3e+K8qOFyclV+D0Ncb4HqEvOKfw=; b=nLz3Z317krzDcM+UskgA99eMfj7TROX93vBbxZqXNFTLFGd0QdJam5EaKXLoCa4FbI x5YmmAC+sZmIFM7TqRuRCsAFzBXwD9yVYzA+W1sf3qFMwzDcUCsOxkfACc5RrZyTaqZW ee+904VzBPzrCMnhaRpnIl2IYkTEvCjhCg+aA= 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=h1sp/5UWnIe4+RWtpJfM4I/BbuV7Ui/fbaO/6BafXsHqiOmZI1038KAoSuDFiREZT6 ZtpKt3XKQEfmBgcOSwJikznot9WctPXMaYYy5HYs7gwqIcNoh89usCzHDAALhLfCnIB9 TJwL7TvRntbxIma96xipm89ogpFgXPZgDynJY= Received: by 10.140.164.1 with SMTP id m1mr2971805rve.69.1223305712522; Mon, 06 Oct 2008 08:08:32 -0700 (PDT) Received: by 10.140.248.12 with HTTP; Mon, 6 Oct 2008 08:08:32 -0700 (PDT) Message-ID: Date: Mon, 6 Oct 2008 09:08:32 -0600 From: "Scott Marlowe" To: Rich Subject: Re: Postgres database as a client/server architecture Cc: "Mohammed Rashid" , pgsql-admin@postgresql.org In-Reply-To: <8fb205ea0810060800t6a14d70bo85bc55dd8db32914@mail.gmail.com> 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/29 X-Sequence-Number: 30485 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...