Re: message type 0x44 - Mailing list pgsql-novice
From | Neil |
---|---|
Subject | Re: message type 0x44 |
Date | |
Msg-id | 6.1.1.1.2.20041208164630.024fc380@mail.hica.com.au Whole thread Raw |
In response to | message type 0x44 (Neil <neil@hica.com.au>) |
List | pgsql-novice |
>Re: >$ pg_dump: message type 0x44 arrived from server while idle >$ pg_dump: dumpClasses(): 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: FETCH 100 FROM _pg_dump_cursor > >Not quite sure what it all means, DB seems to be functioning OK but I am >not convinced I am dumping all the I am expecting to. I have isolated the table that is giving me the problem in pg_dump I am now getting from this error from the command pg_dump -o -a -t contact ourdb ERROR: MemoryContextAlloc: invalid request size 4294967293 pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293 pg_dump: lost synchronization with server, resetting connection pg_dump: SQL command to dump the contents of table "hiclientcontact" failed: PQe ndcopy() failed. pg_dump: Error message from server: ERROR: MemoryContextAlloc: invalid request size 4294967293 pg_dump: The command was: COPY "contact" WITH OIDS TO stdout; [postgres@owen backup]$ DEBUG: pq_flush: send() failed: Broken pipe and I get this with -d DEBUG: server process (pid 6863) was terminated by signal 11 DEBUG: terminating any other active server processes 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. DEBUG: all server processes terminated; reinitializing shared memory and semaph ores DEBUG: database system was interrupted at 2004-12-08 16:11:10 EST DEBUG: checkpoint record is at 1/37C8267C DEBUG: redo record is at 1/37C8267C; undo record is at 0/0; shutdown FALSE DEBUG: next transaction id: 44282241; next oid: 11420991 DEBUG: database system was not properly shut down; automatic recovery in progre ss pg_dump: message type 0x44 arrived from server while idle pg_dump: dumpClasses(): 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: FETCH 100 FROM _pg_dump_cursor [postgres@owen backup]$ DEBUG: redo starts at 1/37C826BC DEBUG: ReadRecord: record with zero length at 1/37C95398 DEBUG: redo done at 1/37C95368 DEBUG: database system is ready TIA Neil
pgsql-novice by date: