Re: Large Objects and Replication question

From: Alexey Klyukin <alexk(at)waki(dot)ru>
To: Howard Cole <howardnews(at)selestial(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Large Objects and Replication question
Date: 2009-12-02 15:18:51
Message-ID: 4C0E0582-7C50-41C2-92DA-047C978716C8@waki.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Dec 2, 2009, at 4:23 PM, Howard Cole wrote:

> Does anyone know of a replication solution that can handle large objects? Preferrably on a per database rather than per cluster basis.

Take a look at Mammoth Replicator: https://projects.commandprompt.com/public/replicator.

Additionally there is a list of available open-source replication solutions here:
http://wiki.postgresql.org/wiki/Replication%2C_Clustering%2C_and_Connection_Pooling

Personally I'm not aware of other solutions supporting large objects, but I'm sure there should be more of them :).

>
> Incidentally - out of interest - why doesn't Slony handle large objects?
>

Here is an excerpt from the Slony documentation:

Slony-I does not automatically propagate schema changes, nor does it have any ability to replicate large objects. There is a single common reason for these limitations, namely that Slony-I collects updates using triggers, and neither schema changes, large object operations, nor TRUNCATE requests are able to have triggers suitable to inform Slony-I when those sorts of changes take place. As a result, the only database objects where Slony-I can replicate updates are tables and sequences.
http://www.slony.info/documentation/slonyintro.html#INTRODUCTION

I'm not sure that it's up-to-date, since 8.4 has at least on truncate triggers, but still there are no triggers on large objects yet.

--
Alexey Klyukin http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-12-02 15:35:22 Re: READ ONLY & I/O ERROR
Previous Message Albe Laurenz 2009-12-02 15:17:03 Re: quote string exactly as it is