On 10/6/2004 9:46 AM, Jan Wieck wrote:

> I was able to reproduce a similar core by using a simple user defined 
> data type that has no comparision operators at all - just input and 
> output functions and nothing else. Slony does not have such data type. 
> The xxid type coming with it is a full blown type that even comes with 
> an opclass for indexing. But tsearch2 has a few of those critters. Could 
> it be that after uninstalling Slony, you also uninstalled and eventually 
> reinstalled tsearch2 in that database?
> 
> However, this is a serious bug since user defined tyes without any 
> operators are of course legal in Postgres and have to be supported by 
> Slony. I am working on a fix for it.

This is fixed in REL_1_0_STABLE and HEAD, so it will be included in the 
upcoming version 1.0.3.

The fix will fallback to compare the external string representation 
returned by SPIgetvalue() if it cannot determine an "=" operator for the 
data type. This will automatically cover array attributes as well. For 
version 1.1 we might want to change this again to use array_eq() instead 
if there is an equal operator for the array elements data type.


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 #