Error while doing a Vacuum

Поиск
Список
Период
Сортировка
От Miguel A. Juan
Тема Error while doing a Vacuum
Дата
Msg-id 002001c16ea5$771a8350$07c8a8c0@miguel2000
обсуждение исходный текст
Список pgsql-bugs
Hello,

I have a problem when I ran a VACUUM on a Postgresql database, I had tried
to do it a few times and  the vacuum always stop in the same place with the
same error (or message), and it takes more than one hour before I got it.
The message that I get is in spanish and it says : No space left on the
device.



PostgreSQL version: 7.1.2
System: RedHat Linux 7.0
Computer PIII 800 Mhz 256 Mg RAM


   665 NOTICE:  --Relation gdinformesm--
   666 NOTICE:  Pages 40221: Changed 0, reaped 26022, Empty 0, New 0; Tup
893413: Vac 896414, Keep/VTL 0/0, Crash 0, UnUsed 85438, MinLen 109, MaxLen
201; Re-using: Free/Avail. Space 172320356/172312672; EndEmpty/Avail. Pages
0/26021. CPU 2.13s/0.68u sec.
   667 NOTICE:  Index i2informesm: Pages 17316; Tuples 893413: Deleted
520320. CPU 2.94s/8.27u sec.
   668 NOTICE:  Index i3informesm: Pages 27041; Tuples 893413: Deleted
520320. CPU 2.70s/7.02u sec.
   669 NOTICE:  Index i4informesm: Pages 10214; Tuples 893413: Deleted
520320. CPU 1.40s/7.29u sec.
   670 NOTICE:  Index i5informesm: Pages 4739; Tuples 893413: Deleted
520319. CPU 1.21s/8.40u sec.
   671 NOTICE:  Index i6informesm: Pages 9873; Tuples 893413: Deleted
520319. CPU 1.26s/7.10u sec.
   672 NOTICE:  Index i7informesm: Pages 14643; Tuples 893413: Deleted
520319. CPU 1.59s/6.44u sec.
   673 NOTICE:  Index i8informesm: Pages 12466; Tuples 893413: Deleted
520319. CPU 1.41s/7.08u sec.
   674 NOTICE:  Index gdinformesm_codiinfo_key: Pages 5133; Tuples 893413:
Deleted 520319. CPU 1.10s/6.94u sec.
   675 NOTICE:  Index i9informesm: Pages 9690; Tuples 893413: Deleted
520319. CPU 1.54s/7.01u sec.
   676 NOTICE:  Index i10informes: Pages 5934; Tuples 893413: Deleted
520319. CPU 1.28s/6.90u sec.
   677 FATAL 2:  ZeroFill(/data/pgsql/pg_xlog/xlogtemp.15100) failed: No
queda espacio en el dispositivo
   678 pqReadData() -- backend closed the channel unexpectedly.
   679  This probably means the backend terminated abnormally
   680  before or while processing the request.
   681 connection to server was lost

Regards,

Miguel Juan
Mallorca (Spain)

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "Patricia Anderson"
Дата:
Сообщение:
Следующее
От: Yuri Gulyaev
Дата:
Сообщение: Can't compile PosgreSql