From: Mohammed Rashid <mail4rashid@gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Rich <rhdyes@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres database as a client/server architecture
Date: Mon, 6 Oct 2008 21:54:21 +0400
Message-ID: <b1bef36d0810061054h99dbc18r5522799465e7a939@mail.gmail.com> (raw)
In-Reply-To: <dcc563d10810060808g3b4149f2odae1de82f28eb805@mail.gmail.com>
References: <b1bef36d0810052323x4bcaf24fmb3a012fc83a002b2@mail.gmail.com>
<dcc563d10810060708o21eebc16nab9b29aed6bd3eb9@mail.gmail.com>
<8fb205ea0810060800t6a14d70bo85bc55dd8db32914@mail.gmail.com>
<dcc563d10810060808g3b4149f2odae1de82f28eb805@mail.gmail.com>
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 <scott.marlowe@gmail.com> wrote:
> On Mon, Oct 6, 2008 at 9:00 AM, Rich <rhdyes@gmail.com> wrote:
>> On Mon, Oct 6, 2008 at 10:08 AM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>>> 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.
>>
>> 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...
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mail4rashid@gmail.com, scott.marlowe@gmail.com, rhdyes@gmail.com
Subject: Re: Postgres database as a client/server architecture
In-Reply-To: <b1bef36d0810061054h99dbc18r5522799465e7a939@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox