*Sigh*, still not having much fun over here:
# gdb /usr/local/pgsql/bin/postgres postgres.36561.core
#0 0x8063b0f in nocachegetattr (tuple=0xbfbfe928, attnum=2,
tupleDesc=0x84ca368, isnull=0xbfbfe7af "") at heaptuple.c:494
494 off = att_addlength(off, att[j]->at
* Tom Lane <[EMAIL PROTECTED]> [001008 18:57] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I should have also said that since this is pretty reproducable I'd
> > be happy to run with patches for stronger assertion checks
>
> If you're not running with --enable-cassert configured, I'
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I should have also said that since this is pretty reproducable I'd
> be happy to run with patches for stronger assertion checks
If you're not running with --enable-cassert configured, I'd certainly
recommend trying that.
reg
* Alfred Perlstein <[EMAIL PROTECTED]> [001008 03:52] wrote:
>
> Unfortunatly I'm still getting crashes, this one looks like it's
> during a vacuum, previously I got a crash while doing an UPDATE, but
> in exactly the same spot, it took quite a bit longer to provoke this
> time:
I should have al
* Alfred Perlstein <[EMAIL PROTECTED]> [001006 16:02] wrote:
> * Tom Lane <[EMAIL PROTECTED]> [001004 09:56] wrote:
> > Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > > I have a reliable way to make postgresql crash after a
> > > couple of hours over here and a backtrace that looks like a good
>
* Tom Lane <[EMAIL PROTECTED]> [001004 09:56] wrote:
> Alfred Perlstein <[EMAIL PROTECTED]> writes:
> > I have a reliable way to make postgresql crash after a
> > couple of hours over here and a backtrace that looks like a good
> > catch.
>
> I'm interested in pursuing this, but the backtrace doe
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I have a reliable way to make postgresql crash after a
> couple of hours over here and a backtrace that looks like a good
> catch.
I'm interested in pursuing this, but the backtrace doesn't give enough
info to debug it. It looks like the backend is
your time,
-Alfred
- Forwarded message from Alfred Perlstein <[EMAIL PROTECTED]> -
From: Alfred Perlstein <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Tom Lane <[EMAIL PROTECTED]>
Subject: [HACKERS] more crashes
Date: Mon, 2 Oct 2000 15:17:12 -0700
Message-ID: <[EMA
This time I'm pretty sure I caught the initial crash during an update:
I disabled the vacuum analyze and still got table corruption with a crash:
two crashdumps of 7.0.2+somepatches
*$Header: /home/pgcvs/pgsql/src/backend/access/common/heaptuple.c,v 1.6
2 2000/04/12 17:14:36 momjian Ex
