Tue Jan 30 05:09:43 PST 2007
- Previous message: [Slony1-general] getting postgresql server crashes with slony
- Next message: [Slony1-general] getting postgresql server crashes with slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jan 29, 2007 at 07:34:36PM -0700, Brian Hirt wrote: > > Is it possible that slony is causing these crashes? I think that It is. With a sig11, though, your best bet is to look at the core file that should be generated. I assume you have compiled with debugging symbols, and that you don't have core file generation turned off. If you can get a backtrace from that core file, it'd be handy. Are you sure, by the way, that Slony and Postgres were compiled by the same compiler, and that Slony was compiled against the right libraries? It's possible to introduce a subtle incompatibility that way. > NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=8572 > CONTEXT: SQL statement "SELECT "_mobycluster".cleanupNodelock()" > PL/pgSQL function "cleanupevent" line 77 at perform > > Are they something to be worried about? No. A -- Andrew Sullivan | ajs at crankycanuck.ca Unfortunately reformatting the Internet is a little more painful than reformatting your hard drive when it gets out of whack. --Scott Morris
- Previous message: [Slony1-general] getting postgresql server crashes with slony
- Next message: [Slony1-general] getting postgresql server crashes with slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list