pg_dumpall failing from possible corrupted shared memory

Поиск
Список
Период
Сортировка
От Richard Broersma Jr
Тема pg_dumpall failing from possible corrupted shared memory
Дата
Msg-id 114069.9815.qm@web31804.mail.mud.yahoo.com
обсуждение исходный текст
Ответы Re: pg_dumpall failing from possible corrupted shared memory  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
I am trying to perform a complete dump of my database.  However, I am getting an error when
pg_dumpall reaches one particular database.  I reformatted the text so that it wouldn't get
chopped to pieces after it is sent.

Here is the output from pg_dumpall:

postgres@db_server01~ $ pg_dumpall > test.dump
pg_dump: SQL command failed
pg_dump: Error message from server:
         server closed the connection unexpectedly
This probably means the server terminated abnormally
         before or while processing the request.
pg_dump: The command was:
   SELECT t.tableoid,
          t.oid,
          t.relname as indexname,
          pg_catalog.pg_get_indexdef(i.indexrelid) as indexdef,
          t.relnatts as indnkeys,
          i.indkey,
          i.indisclustered,
          c.contype,
          c.conname,
          c.tableoid as contableoid,
          c.oid as conoid,
          (SELECT spcname
           FROM pg_catalog.pg_tablespace s
           WHERE s.oid = t.reltablespace) as tablespace
          FROM pg_catalog.pg_index i
          JOIN pg_catalog.pg_class t
          ON (t.oid = i.indexrelid)
          LEFT JOIN pg_catalog.pg_depend d
          ON (d.classid = t.tableoid
              AND d.objid = t.oid
              AND d.deptype = 'i')
          LEFT JOIN pg_catalog.pg_constraint c
          ON (d.refclassid = c.tableoid
              AND d.refobjid = c.oid)
          WHERE i.indrelid = '16737'::pg_catalog.oid
          ORDER BY indexname
pg_dumpall: pg_dump failed on database "mydb", exiting



Here is the output from the logs when these errors occurs minus the repeated above query:

10-25 18:51:43 PDT% LOG:   server process (PID 12899) was
      terminated by signal 11
10-25 18:51:43 PDT% LOG:   terminating any other active
      server processes
10-25 18:51:43 PDT%postgres WARNING:    terminating connection
      because of crash of another server process
10-25 18:51:43 PDT%postgres DETAIL:
      The postmaster has commanded this server process to
      roll back the current transaction and exit, because
      another server process exited abnormally and possibly
      corrupted shared memory.
10-25 18:51:43 PDT%postgres HINT:
      In a moment you should be able to reconnect to the
      database and repeat your command.
10-25 18:51:43 PDT% LOG:  all server processes terminated;
      reinitializing
10-25 18:51:43 PDT% LOG:  database system was interrupted
      at 2006-10-25 18:50:42 PDT
10-25 18:51:43 PDT% LOG:  checkpoint record is at 0/8E2DBA08
10-25 18:51:43 PDT% LOG:  redo record is at 0/8E2DBA08;
      undo record is at 0/0; shutdown TRUE
10-25 18:51:43 PDT% LOG:  next transaction ID: 168758;
      next OID: 621178
10-25 18:51:43 PDT% LOG:  next MultiXactId: 45;
      next MultiXactOffset: 95
10-25 18:51:43 PDT% LOG:  database system was not properly shut down;
      automatic recovery in progress
10-25 18:51:43 PDT% LOG:  record with zero length at 0/8E2DBA4C
10-25 18:51:43 PDT% LOG:  redo is not required
10-25 18:51:43 PDT% LOG:  database system is ready
10-25 18:51:43 PDT% LOG:  transaction ID wrap limit is 1073790580,
      limited by database "postgres"

Any help is appreciated.

Regards,

Richard Broersma Jr.


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

Предыдущее
От: Richard Broersma Jr
Дата:
Сообщение: pg_dumpall failing
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_dumpall failing from possible corrupted shared memory