Tue May 9 07:54:11 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 Tue, May 09, 2006 at 03:48:35PM +0100, Gavin Hamill wrote: > print tab_id tells me $1 is 73, and looking in sl_table shows me that's > our "RoomNight" table.. whose primary "ID" column is specifically > described as NOT NULL.. [. . .] > So there's definately no data stored with a NULL ID - and I tried a > couple of sample queries to see if I could force a crash... Have you in fact had some _other_ crash of the system? I'd do a REINDEX to confirm this. You won't actually get any results form your queries if you have data corruption that has resulted in a NULL value in a NOT NULL index, but you'll get an error during your reindex. And yes, we've seen this, but we blamed it on faulty hardware. 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] 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