Re: Postgres database as a client/server architecture

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Mohammed Rashid" <mail4rashid(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres database as a client/server architecture
Date: 2008-10-06 14:08:23
Message-ID: dcc563d10810060708o21eebc16nab9b29aed6bd3eb9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2008-10-06 14:12:16 Re: sql command strange behaviour
Previous Message Scott Marlowe 2008-10-06 14:06:01 Re: Shared_buffers hint