Wed Oct 6 17:33:20 PDT 2004
- Previous message: [Slony1-general] slony causes postgresql children to die
- Next message: [Slony1-general] slony causes postgresql children to die
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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? No, I didn't touch the tsearch2 installation. I can only reproduce this bug on my production server (unfortunately), so I'd know immediately if I had purged the tsearch2 functionality. :) > However, this is a serious bug since user defined types without any > operators are of course legal in Postgres and have to be supported by > Slony. I am working on a fix for it. Excellent, thank you! -Brad
- Previous message: [Slony1-general] slony causes postgresql children to die
- Next message: [Slony1-general] slony causes postgresql children to die
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list