Re: Still crashing with latest 7.0.2 (Re: (forw) [HACKERS] more crashes)

2000-10-08 Thread Alfred Perlstein
* 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'

Re: Still crashing with latest 7.0.2 (Re: (forw) [HACKERS] more crashes)

2000-10-08 Thread Tom Lane
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

Re: Still crashing with latest 7.0.2 (Re: (forw) [HACKERS] more crashes)

2000-10-08 Thread Alfred Perlstein
* 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

Still crashing with latest 7.0.2 (Re: (forw) [HACKERS] more crashes)

2000-10-08 Thread Alfred Perlstein
* 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 >

Re: (forw) [HACKERS] more crashes

2000-10-06 Thread Alfred Perlstein
* 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

Re: (forw) [HACKERS] more crashes

2000-10-04 Thread Tom Lane
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

(forw) [HACKERS] more crashes

2000-10-04 Thread Alfred Perlstein
I just wanted to repost this one more time in case developers didn't catch it. 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. My apologies if this one time to many, I won't be posting it again. thanks for your time,