The following failures in the regression tests have started appearing in the
last couple of days in the sanity_check test:
====== sanity_check ======
1a2,3
> NOTICE: AbortTransaction and not in in-progress state
> NOTICE: AbortTransaction and not in in-progress state
6,32c8,9
< relname |relhasindex
< --------------+-----------
< bt_f8_heap |t
< bt_i4_heap |t
< bt_name_heap |t
< bt_txt_heap |t
[...]
< shighway |t
< tenk1 |t
< tenk2 |t
< (23 rows)
<
---
> NOTICE: AbortTransaction and not in in-progress state
> NOTICE: AbortTransaction and not in in-progress state
The VACUUM command against the regression data base fails with the following
error messages:
[...]
DEBUG: --Relation circle_tbl--
DEBUG: Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 6: Vac 0, Crash 0,
Un
Used 0, MinLen 64, MaxLen 64; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail.
P
ages 0/0. Elapsed 0/0 sec.
DEBUG: --Relation timespan_tbl--
DEBUG: Pages 1: Changed 0, Reapped 0, Empty 0, New 0; Tup 10: Vac 0, Crash 0,
U
nUsed 0, MinLen 52, MaxLen 52; Re-using: Free/Avail. Space 0/0; EndEmpty/Avail.
Pages 0/0. Elapsed 0/0 sec.
ERROR: cannot write block 0 of circle_tbl [regression] blind
NOTICE: AbortTransaction and not in in-progress state
ERROR: cannot write block 0 of circle_tbl [regression] blind
NOTICE: AbortTransaction and not in in-progress state
Running the VACUUM command manually in the regression data base fails but at
different blocks in different tables (no obvious pattern in blocks and tables).
Once vacuum runs and fails, any query in the database will fail with the:
NOTICE: AbortTransaction and not in in-progress state
NOTICE: AbortTransaction and not in in-progress state
messages displayed. Re-connecting to the database (i.e. '\c regression')
allows the queries to succeed (until vacuum is executed).
Any help will be greatly appreciated.
--
____ | Billy G. Allie | Domain....: Bill.Allie@mug.org
| /| | 7436 Hartwell | Compuserve: 76337,2061
|-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie@email.msn.com
|/ |LLIE | (313) 582-1540 |
