8.2 instance that won't come up after shutdown

Поиск
Список
Период
Сортировка
От Abraham, Danny
Тема 8.2 instance that won't come up after shutdown
Дата
Msg-id D460EBE8A3D1D246830283AE0478D8FED7BC2F256D@HOUCCRPRD01.adprod.bmc.com
обсуждение исходный текст
Ответы Re: 8.2 instance that won't come up after shutdown  (Scott Marlowe <scott.marlowe@gmail.com>)
Список pgsql-general
Hi

We have a PG version 8.2  instance that won't come up after shutdown. The log shows the following:

2009-06-12 21:39:02.669 MDTLOG:  database system was shut down at 2009-06-12 20:56:51 MDT
2009-06-12 21:39:02.748 MDTLOG:  checkpoint record is at 9/D712F330
2009-06-12 21:39:02.748 MDTLOG:  redo record is at 9/D712F330; undo record is at 0/0; shutdown TRUE
2009-06-12 21:39:02.748 MDTLOG:  next transaction ID: 0/8239765; next OID: 25433
2009-06-12 21:39:02.748 MDTLOG:  next MultiXactId: 1; next MultiXactOffset: 0
2009-06-12 21:39:02.838 MDTLOG:  database system is ready
2009-06-12 21:39:02.846 MDTFATAL:  invalid memory alloc request size 8455717278
2009-06-12 21:39:02.862 MDTLOG:  startup process (PID 6198) exited with exit code 1
2009-06-12 21:39:02.864 MDTLOG:  aborting startup due to startup process failure
2009-06-12 21:39:02.928 MDTLOG:  logger shutting down

We tried to set the autovacuum parameter value to off but unfortunately it did not help

1. Is this bug defined for the 8.2.4 code line also (We know that it is defined for 8.1.X) 2. How can we recreate the
problem?
3. Is there a fix for that bug?

Any help will be appreciated.

Best regards,
Danny Abraham


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Killing a data modifying transaction
Следующее
От: Joel Nothman
Дата:
Сообщение: Re: Select ranges based on sequential breaks