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=Z4c/Fn94MTXprfEn4tgJFoI/xWLU0Ndw1CrBZu1uqxX5IZII2OLLRPqFRIdzKwqt+T
	+1G1ALL50lunE2bNFk85lZY7t2oz+He0OE4hNObdUpiM9x3NtOromex8w6fsmJOJtCpL
	BV+rscyy6HKNPGWI4DWwgC/9viu84/G88VjsU=
Message-ID: <dcc563d10810060708o21eebc16nab9b29aed6bd3eb9@mail.gmail.com>
Date: Mon, 6 Oct 2008 08:08:23 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Mohammed Rashid" <mail4rashid@gmail.com>
Subject: Re: Postgres database as a client/server architecture
Cc: pgsql-admin@postgresql.org
In-Reply-To: <b1bef36d0810052323x4bcaf24fmb3a012fc83a002b2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <b1bef36d0810052323x4bcaf24fmb3a012fc83a002b2@mail.gmail.com>

On Mon, Oct 6, 2008 at 12:23 AM, Mohammed Rashid <mail4rashid@gmail.com> 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.