vacuum crash
Here is a modified version of the vacuum crash I am studying.
Interesting is that if I do a 'vacuum getting' instead of 'select * from
getting;vacuum;', I see a different error message. Rather than a crash
due to an Assert(), psql shows:
NOTICE: AbortTransaction and not in in-progress state
NOTICE: AbortTransaction and not in in-progress state
and the postmaster log file shows:
ERROR: cannot write block -1 of [] blind
AbortCurrentTransaction
NOTICE: AbortTransaction and not in in-progress state
This can be debugged by commenting out the psql command at the end,
running the script, and then running a backend from gdb and doing
'vacuum getting'.
This looks like it may be easier to track down. Vadim, any chance you
can bail me out here, again.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026Attachments:
Here is a modified version of the vacuum crash I am studying.
Interesting is that if I do a 'vacuum getting' instead of 'select *
from getting;vacuum;', I see a different error message. Rather than a
crash due to an Assert(), psql shows:
NOTICE: AbortTransaction and not in in-progress state
NOTICE: AbortTransaction and not in in-progress state
and the postmaster log file shows:
ERROR: cannot write block -1 of [] blind
AbortCurrentTransaction
NOTICE: AbortTransaction and not in in-progress state
This can be debugged by commenting out the psql command at the end,
running the script, and then running a backend from gdb and doing
'vacuum getting'.
Well Oleg, you are not alone now. Others are seeing your problem, so it
is much more likely to be fixed than when it was just one person
reporting the symptom. If you are familiar with backend code then
perhaps you could help track down the problem. If you aren't familiar
with it, you may be interested in volunteering to test patches from
Bruce. This would be especially helpful since you have a real talent for
demonstrating this problem :)
- Tom
On Thu, 8 Oct 1998, Thomas G. Lockhart wrote:
Date: Thu, 08 Oct 1998 06:33:50 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Bruce Momjian <maillist@candle.pha.pa.us>,
PostgreSQL-development <hackers@postgreSQL.org>
Subject: Re: [HACKERS] vacuum crashHere is a modified version of the vacuum crash I am studying.
Interesting is that if I do a 'vacuum getting' instead of 'select *
from getting;vacuum;', I see a different error message. Rather than a
crash due to an Assert(), psql shows:
NOTICE: AbortTransaction and not in in-progress state
NOTICE: AbortTransaction and not in in-progress state
and the postmaster log file shows:
ERROR: cannot write block -1 of [] blind
AbortCurrentTransaction
NOTICE: AbortTransaction and not in in-progress state
This can be debugged by commenting out the psql command at the end,
running the script, and then running a backend from gdb and doing
'vacuum getting'.Well Oleg, you are not alone now. Others are seeing your problem, so it
is much more likely to be fixed than when it was just one person
reporting the symptom. If you are familiar with backend code then
perhaps you could help track down the problem. If you aren't familiar
with it, you may be interested in volunteering to test patches from
Bruce. This would be especially helpful since you have a real talent for
demonstrating this problem :)- Tom
Unfortunately I'm not familiar with backend code but would happy
to test everything as soon as patches will be available.
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83