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(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Responses

• Re: [HACKERS] vacuum crash at 1998-10-08 06:33:50 from Thomas G. Lockhart

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 1998-10-08 00:08:37
	Subject: Re: [HACKERS] Dumping of views -- done!
Previous:	From: Peter T Mount	Date: 1998-10-07 21:51:26
	Subject: Missing file from JDBC Driver