From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Silverman <noah@allresearch.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: WEIRD CRASH?!?!
Date: Fri, 24 Jan 2003 20:04:07 -0500
Message-ID: <28079.1043456647@sss.pgh.pa.us> (raw)
In-Reply-To: <6F2E6C98-2FFA-11D7-A3A3-000393AA8F3C@allresearch.com>
References: <6F2E6C98-2FFA-11D7-A3A3-000393AA8F3C@allresearch.com>
Noah Silverman <noah@allresearch.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, noah@allresearch.com, josh@agliodbs.com
Subject: Re: WEIRD CRASH?!?!
In-Reply-To: <28079.1043456647@sss.pgh.pa.us>
References: <6F2E6C98-2FFA-11D7-A3A3-000393AA8F3C@allresearch.com> <28079.1043456647@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox