Re: Single Instance of Backend

From: weigelt(at)metux(dot)de
To: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Single Instance of Backend
Date: 2003-06-19 11:12:25
Message-ID: 20030619111225.GA616@metux.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jun 18, 2003 at 12:58:45PM -0700, Dennis Gearon wrote:

<snip>
> To make clustering work, and be as redundant as possible, how do the
> clustering solutions work for:
>
> Postgres?

i've integrated clustering support into my own db abstraction in php.
the idea behind: evry table has an inode_id (global object id) and
a mtime field. my db-layer generates all the queries (the application
only sees whole objects and does not speak sql anymore). on object
creation a new inode_id is fetched from an sequence, and the mtime
is updated on each write operation. from time to time (i.e. once per
minute) an poller script runs over the db, fetches all new tuples
and posts them to the other nodes.

not very performant, but works quite good.

cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux ITS
Webhosting ab 5 EUR/Monat. UUCP, rawIP und vieles mehr.

phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact(at)metux(dot)de
cellphone: +49 174 7066481 smsgate: sms(dot)weigelt(at)metux(dot)de
---------------------------------------------------------------------
Diese Mail wurde mit UUCP versandt. http://www.metux.de/uucp/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Justin Clift 2003-06-19 11:23:03 [Fwd: PostGreSQL information]
Previous Message Bruno Wolff III 2003-06-19 10:58:55 Re: Incremental backups, and backup history