On 7/26/2006 4:07 AM, Csaba Nagy wrote:

> I could do this, but I have to support oracle too and at least at some
> higher level the behavior should be the same from the application POV.
> This might be a PITA...
> 
> But I guess I'll go for it as there's no better choice.

You can allways go the open source way and hire some developer who will 
fix BLOB's shortcomings, contribute that to Postgres and then either 
reopen the discussion based on the new functionality or have the same 
developer continue working for you and contribute the BLOB support to 
the Slony project.

That is BTW exactly how Slony-I came into existence. So this isn't meant 
as a snippy comment but rather serious. I am working fulltime on 
Postgres and Slony because the company I am working for needs these 
things. We are not a software company, just a Postgres user. We 
contribute all my work to the community because there might be other 
Postgres users out there who have similar needs and can contribute 
something in return.

It is important to understand that while Postgres and Slony are open 
source products free of charge, they are not a free lunch. It is the 
users responsibility to ensure that these products will continue to fit 
their needs in the future. Funding developers to work on the specific 
details you need is a good way to do that.


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 #