[PORTS] Backend crash during vacuum
Maarten Boekhold
PostgreSQL version 6.3.2
BSD/I 2.1
I get a crash when I vacuum a specific table. The error-message:
NOTICE: Rel product: Pages 13639: Changed 7, Reapped 2057, Empty 0, New
0; Tup 608429: Vac 109679, Crash 109679, UnUsed 371, MinLen 106, MaxLen
202; Re-using: Free/Avail. Space 16393624/16393624; EndEmpty/Avail. Pages
0/2057. Elapsed 3/3 sec.
NOTICE: Ind product_aroms_idx: Pages 2681; Tuples 608429: Deleted 343.
Elapsed 0/4 sec.
NOTICE: Ind product_artit_idx: Pages 2939; Tuples 608429: Deleted 343.
Elapsed 1/3 sec.
NOTICE: Ind product_arart_idx: Pages 1529; Tuples 608429: Deleted 331.
Elapsed 0/4 sec.
Too Large Allocation Request("!(0 < (size) &&
(size) <= (0xfffffff)):size=0 [0x0]", File: "mcxt.c", Line: 232)
!(0 < (size) && (size) <= (0xfffffff)) (0) [Inappropriate ioctl for device]
There are 3 indices on this table. Doesn't the fact that there are
messages for all 3 indices mean that they are all already processed?
product_aroms_idx is an index on varchar(25)
product_artit_idx is an index on varchar(25)
product_arart_idx is an index on int4
Any clue what might be causing this?
Maarten
_____________________________________________________________________________
| TU Delft, The Netherlands, Faculty of Information Technology and Systems |
| Department of Electrical Engineering |
| Computer Architecture and Digital Technique section |
| M.Boe...@et.tudelft.nl |
-----------------------------------------------------------------------------
Maarten Boekhold
> Too Large Allocation Request("!(0 < (size) &&
> (size) <= (0xfffffff)):size=0 [0x0]", File: "mcxt.c", Line: 232)
> !(0 < (size) && (size) <= (0xfffffff)) (0) [Inappropriate ioctl for device]
I hate to follow-up on my own mail, but I get this message not only when
vacuuming, but also for a lot of queries. Dunno why, just plain selects,
with only one where-clause. One query works, and then some other one
doesn't. It doesn't make any difference in which order I do the queries.
The table was freshly loaded, with new indices created on them
afterwards. I'm now reloading the table, and will vacuum it first now
before I create ther indices, but I don't suspect any differences.
Vadim Mikheev
>
> I get a crash when I vacuum a specific table. The error-message:
>
> NOTICE: Rel product: Pages 13639: Changed 7, Reapped 2057, Empty 0, New
> 0; Tup 608429: Vac 109679, Crash 109679, UnUsed 371, MinLen 106, MaxLen
It's bad... I would recommend to re-create indices - they aren't
stable in server crashes -:((
Vadim