Bug #538: Backend crasches
От | pgsql-bugs@postgresql.org |
---|---|
Тема | Bug #538: Backend crasches |
Дата | |
Msg-id | 200112140943.fBE9hIe71504@postgresql.org обсуждение исходный текст |
Список | pgsql-bugs |
Holubniak Piotr (Piotr.Holubniak@cupr.com.pl) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description Backend crasches Long Description My system is running on Pentium II 350 with 128 MB memory, WD-SCSI linux Mandrake 6.0, kernel 2.2.9-27mdk, glibc 1.2.3 Sending query causes backend crash with error: qReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally before or whileprocessing the request. ---------------------------------------------------------------- vacumdb -z visadb - causes backend crash with following information from postmaster DEBUG: --Relation archiwum_pierwotne_transakcji-- DEBUG: Pages 3336: Changed 0, reaped 18, Empty 0, New 0; Tup 76125: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 28, MinLen 328,MaxLen 364; Re-using: Free/Avail. Space 9432/3312; EndEmpty/Avail. Pages 0/10. CPU 0.33s/0.05u sec. DEBUG: Index archiwum_pierwotne_tr_index_key: Pages 243; Tuples 76125: Deleted 0. CPU 0.02s/0.15u sec. DEBUG: Index at_index_index: Pages 243; Tuples 76125: Deleted 0. CPU 0.01s/0.18u sec. DEBUG: Index at_account_number_index: Pages 365; Tuples 76125: Deleted 0. CPU 0.06s/0.20u sec. DEBUG: Index at_data_pliku_index: Pages 240; Tuples 76125: Deleted 0. CPU 0.04s/0.18u sec. DEBUG: Rel archiwum_pierwotne_transakcji: Pages: 3336 --> 3336; Tuple(s) moved: 0. CPU 0.00s/0.02u sec. DEBUG: Analyzing... ERROR: MemoryContextAlloc: invalid request size 1970234211 Server process (pid 1781) exited with status 11 at Fri Dec 14 11:30:21 2001 Terminating any active server processes... The Data Base System is in recovery mode NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. Server processes were terminated at Fri Dec 14 11:30:21 2001 Reinitializing shared memory and semaphores The Data Base System is starting up DEBUG: database system was interrupted at 2001-12-14 11:27:49 CET DEBUG: CheckPoint record at (0, 1623325932) DEBUG: Redo record at (0, 1623325932); Undo record at (0, 0); Shutdown TRUE DEBUG: NextTransactionId: 434550; NextOid: 1422825 DEBUG: database system was not properly shut down; automatic recovery in progress... DEBUG: redo starts at (0, 1623325996) DEBUG: ReadRecord: record with zero len at (0, 1623677456) DEBUG: redo done at (0, 1623677420) The Data Base System is starting up ---------------------------------------------------------------- database contains about 1,000,000 records Relation archiwum_pierwotne_transakcji contains 76117 records Sample Code SELECT K.numer_oddzialu, K.nazwisko_posiadacza_karty, K.imie_posiadacza_karty, K.numer_karty, A.data_pliku,A.data_zaciagniecia,S.typ_operacji, A.purchase_date, A.transaction_code, S.kod_statusu,A.destination_amount, K.numer_modulo_rachunku, S.data_wyslania, S.index, A.merchant_city,S.kod_bledu,A.source_currency_code, A.destination_currency_code FROM karty K, archiwum_pierwotne_transakcji A, spooler S WHERE ((A.index = S.index_pierwotny)AND (A.account_number = K.numer_karty) AND (S.typ_operacji=1)) AND (K.numer_karty = 4408070000137888) No file was uploaded with this report
В списке pgsql-bugs по дате отправления:
Предыдущее
От: Lamar OwenДата:
Сообщение: Re: Bug #537: In Red Hat don't open port 5432 and PostgreSql
Следующее
От: pgsql-bugs@postgresql.orgДата:
Сообщение: Bug #539: Unexpected DeadLock on REFERENCES