Skip site navigation (1) Skip section navigation (2)

Re: Postgres database as a client/server architecture

From: Montaseri <montaseri(at)gmail(dot)com>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: Rich <rhdyes(at)gmail(dot)com>, "Mohammed Rashid" <mail4rashid(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres database as a client/server architecture
Date: 2008-10-06 18:34:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
I'd say, don't overwhelm the original ask-er. Let him explain this problem
statement again.
So far we know he wants a client server.
Do you want thin client (like web based) or thick like X11 or Java or VB
Do you want the data processing be  on the server (more reliable but
slower), or do you want some of the processing on the client (faster but
more complex)?


On Mon, Oct 6, 2008 at 8:08 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> On Mon, Oct 6, 2008 at 9:00 AM, Rich <rhdyes(at)gmail(dot)com> wrote:
> > On Mon, Oct 6, 2008 at 10:08 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
> wrote:
> >> 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.
> >
> > 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...
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:

In response to


pgsql-admin by date

Next:From: Jonah H. HarrisDate: 2008-10-06 18:45:18
Subject: Re: Postgres database as a client/server architecture
Previous:From: Mohammed RashidDate: 2008-10-06 17:54:21
Subject: Re: Postgres database as a client/server architecture

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group