Re: Vacuum problem on large table - Mailing list pgsql-general

From Tom Lane
Subject Re: Vacuum problem on large table
Date
Msg-id 21276.991779670@sss.pgh.pa.us
Whole thread Raw
In response to Vacuum problem on large table  (mordicus <mordicus@free.fr>)
List pgsql-general
mordicus <mordicus@free.fr> writes:
> vacuum verbose analyse record_blob;
> NOTICE:  --Relation record_blob--
> NOTICE:  Pages 62437: Changed 0, reaped 0, Empty 0, New 0; Tup 1005540: Vac
> 0, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 80, MaxLen 2032; Re-using:
> Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 4.57s/0.37u sec.
> NOTICE:  --Relation pg_toast_44260091--
> NOTICE:  Pages 1: Changed 0, reaped 0, Empty 0, New 0; Tup 2: Vac 0,
> Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 63, MaxLen 2034; Re-using:
> Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU 0.00s/0.00u sec.
> NOTICE:  Index pg_toast_44260091_idx: Pages 2; Tuples 2. CPU 0.00s/0.00u
> sec.
> NOTICE:  Analyzing...
> ERROR:  Memory exhausted in AllocSetAlloc(875769886)

This looks like corrupt data --- specifically, a varlena value with a
ridiculous length word --- in your table.  Hard to say more with so
little information.

            regards, tom lane

pgsql-general by date:

Previous
From: "Thalis A. Kalfigopoulos"
Date:
Subject: Re: PostgreSQL and TPC benchmarks
Next
From: Stephan Richter
Date:
Subject: Re: setting PGDATESTYLE