Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 4C77D47613F for ; Fri, 24 Jan 2003 20:09:59 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D697F4764C9 for ; Fri, 24 Jan 2003 20:04:26 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0P1475u028080; Fri, 24 Jan 2003 20:04:08 -0500 (EST) To: Noah Silverman Cc: josh@agliodbs.com, pgsql-performance@postgresql.org Subject: Re: WEIRD CRASH?!?! In-reply-to: <6F2E6C98-2FFA-11D7-A3A3-000393AA8F3C@allresearch.com> References: <6F2E6C98-2FFA-11D7-A3A3-000393AA8F3C@allresearch.com> Comments: In-reply-to Noah Silverman message dated "Fri, 24 Jan 2003 19:17:48 -0500" Date: Fri, 24 Jan 2003 20:04:07 -0500 Message-ID: <28079.1043456647@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/308 X-Sequence-Number: 955 Noah Silverman writes: > One clue. > I actually moved the pg_xlog directory to another drive and then > symbolically linked it back to the data directory. Uh, did you have the postmaster shut down while you did that? This looks like a collision between two processes both trying to create the next segment of the xlog at about the same time. But there are interlocks that are supposed to prevent that. I don't think you need to worry about the integrity of your data; the panic reset should put everything right. But I'd sure be interested if you can reproduce this problem. regards, tom lane