Re: Restore killing the backend - Mailing list pgsql-general

From Stephen Bacon
Subject Re: Restore killing the backend
Date
Msg-id 5.1.0.14.0.20020731152616.01da1ce0@mailhost.13x.com
Whole thread Raw
In response to Restore killing the backend  (Stephen Bacon <sbacon@13x.com>)
Responses Re: Restore killing the backend
List pgsql-general
Hello *again*
strangeness...something seems to be stripping the logs off the bottom of my
last two posts (so I'm trying a different email client).
Here's the third try - appologies for the wasted bandwidth.
-Steve


<crash with defaul WAL settings>

[[[output from psql attempting import]]]

<snip>

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
'tbloutdischassess_pkey' for table 'tbloutdischassess'
CREATE
NOTICE: copy: line 4232076, 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 closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
lost synchronization with server, resetting connection
connection to server was lost

[[[and a second attempt:]]]

<snip>

NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
'tblnatldischtier_pkey' for table 'tblnatldischtier'
CREATE
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
'tbloutdischassess_pkey' for table 'tbloutdischassess'
CREATE
ERROR: copy: line 5706, pg_atoi: error in ""3835": can't parse ""3835"
lost synchronization with server, resetting connection
ERROR: copy: line 1008, Bad float4 input format 'LN'
lost synchronization with server, resetting connection
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
lost synchronization with server, resetting connection
connection to server was lost


[[[ level 2 debug messages ]]]

DEBUG:  shmem_exit(0)
DEBUG:  exit(0)
DEBUG:  reaping dead processes
DEBUG:  child process (pid 11024) exited with exit code 0
DEBUG:  recycled transaction log file 0000000000000025
DEBUG:  recycled transaction log file 0000000000000026
DEBUG:  recycled transaction log file 0000000000000024
DEBUG:  proc_exit(0)
DEBUG:  shmem_exit(0)
DEBUG:  exit(0)
DEBUG:  reaping dead processes
DEBUG:  child process (pid 11025) exited with exit code 0
FATAL 2:  XLogWrite: write request 0/2D10C000 is past end of log 0/2D0FE000
DEBUG:  proc_exit(2)
DEBUG:  shmem_exit(2)
DEBUG:  exit(2)
DEBUG:  reaping dead processes
DEBUG:  child process (pid 11026) exited with exit code 2
DEBUG:  server process (pid 11026) exited with exit code 2
DEBUG:  terminating any other active server processes
DEBUG:  CleanupProc: sending SIGQUIT to process 11009
NOTICE:  copy: line 4232076, 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:  reaping dead processes
DEBUG:  child process (pid 11009) exited with exit code 1
DEBUG:  all server processes terminated; reinitializing shared memory and
semaphores
DEBUG:  shmem_exit(0)
invoking IpcMemoryCreate(size=728809472)

[[[ level 2 debug messages w/ increased WAL buffers ]]]

<snip>

DEBUG: StartTransactionCommand
DEBUG: query: COPY "tblirfpai_quality" FROM stdin;
DEBUG: ProcessUtility: COPY "tblirfpai_quality" FROM stdin;
DEBUG: reaping dead processes
DEBUG: child process (pid 4433) was terminated by signal 11
DEBUG: server process (pid 4433) was terminated by signal 11
DEBUG: terminating any other active server processes
DEBUG: all server processes terminated; reinitializing shared memory and
semaphores
DEBUG: shmem_exit(0)
invoking IpcMemoryCreate(size=417505280)
DEBUG: database system was interrupted at 2002-07-31 14:21:39 EDT
DEBUG: checkpoint record is at 1/9400808C
DEBUG: redo record is at 1/9300702C; undo record is at 0/0; shutdown FALSE
DEBUG: next transaction id: 1778; next oid: 39371344
DEBUG: database system was not properly shut down; automatic recovery in
progress
DEBUG: redo starts at 1/9300702C
DEBUG: reaping dead processes
DEBUG: startup process (pid 4434) was terminated by signal 11
DEBUG: aborting startup due to startup process failure
DEBUG: proc_exit(1)
DEBUG: shmem_exit(1)DEBUG: exit(1)


pgsql-general by date:

Previous
From: Stephen Bacon
Date:
Subject: Re: Restore killing the backend
Next
From: Andrew Sullivan
Date:
Subject: Re: Restore killing the backend