[Bucardo-general] Sync of fields with user-function as default, Sync of XML fields

[Greg Sabino Mullane]

On Mon, Sep 06, 2010 at 04:15:45PM +0200, Franz Dürr wrote:

> I managed to solve the 'DBD::Pg::st execute failed: ERROR:  could
> not identify an equality operator for type xml' - problem (thanks to
> Tom Lane for pointing me into the right direction): Bucardo compares
> complete records for equality, and the underlying PostgreSQL
> function 'record_eq()' doesn't care about user-defined operators. To
> let it work with XML-fields, you have to create an operator class
> for XML:

Excellent. Just for the record, the recent patch to the mailing 
list using DISTINCT ON may fix this problem as well. As will using 
Bucardo version 5 (when it comes out).

> Another thing that gave me errors during syncs was that user
> 'bucardo' doesn't have the public-schema in it's search_path. (I
> call functions from schema public in my table constraints)
> 'ALTER USER bucardo SET search_path = bucardo,public;'
> fixed that ok. I just wonder, why bucardo.schema sets bucardo's
> search path to 'bucardo' only, as 'public' should normally always be
> in the search_path.

Not everybody has the 'public' schema, so it's not safe to set it 
like that. It's also a safety mechanism as we don't normally *want* 
bucardo to see anything other than what is in the bucardo schema 
(and the pg_catalog schema of course).

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20110702/05a37731/attachment.bin