Fri Apr 30 09:11:31 PDT 2010
- Previous message: [Slony1-general] encoding problems
- Next message: [Slony1-general] encoding problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leon Mergen wrote: > Hello Steve, > > On Fri, Apr 30, 2010 at 5:39 PM, Steve Singer <ssinger at ca.afilias.info> wrote: >>> I will try to find out what log entry is causing the trouble. >>> >> Do the tables that these errors come from typically get large insert/update >> statements or small ones? >> >> (this is directed at anyone who's seen the issue) > > I'm still trying to isolate the issue a bit, but at the moment it > looks like this issue is triggered by a very large INSERT statement > (as in, a statement with a very large value); > > Regards, > Your issue with the larger values are being caused by an attempt at removing a memory leak checked into 2.0.3 that free's memory a bit too soon. I will post a patch for this later today. I think the INSERT statement is being corrupted causing invalid characters to be put in. What Devrim's is seeing where the initial copy fails would be a different issue. > Leon Mergen -- Steve Singer Afilias Canada Data Services Developer 416-673-1142
- Previous message: [Slony1-general] encoding problems
- Next message: [Slony1-general] encoding problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list