On 7/25/2006 4:09 AM, Csaba Nagy wrote:

>> The problem is there is no way to catch the lo_import(). And if you could, I'm 
>> not sure you could preserve the oid of the LO between nodes. All of this puts 
>> you down the path of replicating LO's at the application level I'd think.
> 
> Well, I wouldn't do it that way. What would work for me:

I don't think it is reasonable to support blobs directly in Slony. They 
are not well supported in Postgres to begin with (no triggers, no 
back-link to table, no possible referential integrity, backup/recovery 
problems).

A possible way would be to move to bytea. I do understand that you don't 
want to deal with the whole blob data in memory at once, but who said 
that you have to store the whole object in one bytea column? It is well 
possible to create a separate table that holds chunks of that data, and 
the application can access them via cursor. That's close enough to large 
object reading in my book. And it fully supports insert/update/delete 
and replication via Slony-I.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #