Mon May 15 04:21:09 PDT 2006
- Previous message: [Slony1-general] Segfault with Slony 1.1.5 and PG 8.1.3 on x86_64
- Next message: [Slony1-general] Segfault with Slony 1.1.5 and PG 8.1.3 on x86_64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, May 15, 2006 at 10:15:13AM +0100, Gavin Hamill wrote: > Alas, a REINDEX of the affected table showed no output on the > commandline or in the logs, and I'm still seeing fairly regular (roughly > once a day) segfaults with exactly the same output from dmesg: Hrm. I'd still bet on data corruption. You might try walking through the table, getting all the data, in chunks, and see if you get a failure. Why does this happen roughly once a day? A -- Andrew Sullivan | ajs at crankycanuck.ca It is above all style through which power defers to reason. --J. Robert Oppenheimer
- Previous message: [Slony1-general] Segfault with Slony 1.1.5 and PG 8.1.3 on x86_64
- Next message: [Slony1-general] Segfault with Slony 1.1.5 and PG 8.1.3 on x86_64
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list