Re: PostgreSQL XID exceeded crash. - Mailing list pgsql-general

From Mario Lopez
Subject Re: PostgreSQL XID exceeded crash.
Date
Msg-id 44FC19C5.5020309@lar3d.com
Whole thread Raw
In response to Re: PostgreSQL XID exceeded crash.  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: PostgreSQL XID exceeded crash.  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
Hi Alvaro,

Ok, maybe is not a crash  but this issue makes postgresql reap all of
it's child processes and restart operations, after this error I get in
pg_restore this message:

pg_restore: [archivador (bd)] Error durante PROCESAMIENTO DE TABLA DE
CONTENIDOS:
pg_restore: [archivador (bd)] Error en entrada de la tabla de contenidos
1893; 0 1615776 TABLE DATA xxxxx postgres
pg_restore: [archivador (bd)] could not execute query: server closed the
connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
    Command was: INSERT INTO xxxxx VALUES (1755298, 2, 117, 28, 1155,
52457, 1, 1, '', '', '', '', NULL);
pg_restore: [archivador (bd)] could not execute query: sin resultado
desde el servidor

I have a attached a log from the XID exhausted resources till it reaps
all of it's child processes, which ends in a crash from pg_restore or
any application using this table.

Thanks.

Alvaro Herrera escribió:
> Mario Lopez wrote:
>
>> Hi!,
>>
>> I am having an XID issue with PostgreSQL, while doing a pg_restore from
>> a 200MB saved database I get a server crash, searching through the debug
>> messages I have found that PostgreSQL crashes due to a exausted XID
>> resource with a message that looks this way (sorry for the Spanish log)
>>
>> UBICACIÓN:  StartupXLOG, xlog.c:4820
>> LOG:  00000: el límite para el reciclaje de ID de transacciones es
>> 2147484146, limitado por base de datos «postgres»
>>
>
> This is not a problem.  If you see a crash, the message is elsewhere --
> the message should start with ERROR, FATAL or PANIC.  LOG is normal
> operation.  I suggest you look at the log more closely.
>
> Maybe the error is the line above; LOCATION lines (UBICACIÓN) are
> located just below the log entry they are annotating.
>
>
DEBUG:  00000: StartTransactionCommand
UBICACI�N:  start_xact_command, postgres.c:1983
DEBUG:  00000: StartTransaction
UBICACI�N:  ShowTransactionState, xact.c:3930
DEBUG:  00000: name: unnamed; blockState:       DEFAULT; state: INPROGR, xid/subid/cid: 273609597/1/0, nestlvl: 1,
children:<> 
UBICACI�N:  ShowTransactionStateRec, xact.c:3955
DEBUG:  00000: reaping dead processes
UBICACI�N:  reaper, postmaster.c:2021
DEBUG:  00000: proceso de servidor (PID 31622) termin� con c�digo de salida 255
UBICACI�N:  LogChildExit, postmaster.c:2419
LOG:  00000: proceso de servidor (PID 31622) termin� con c�digo de salida 255
UBICACI�N:  LogChildExit, postmaster.c:2419
LOG:  00000: terminando todos los otros procesos de servidor activos
UBICACI�N:  HandleChildCrash, postmaster.c:2309
DEBUG:  00000: sending SIGQUIT to process 31308
UBICACI�N:  HandleChildCrash, postmaster.c:2362
DEBUG:  00000: sending SIGQUIT to process 31309
UBICACI�N:  HandleChildCrash, postmaster.c:2396
DEBUG:  00000: reaping dead processes
UBICACI�N:  reaper, postmaster.c:2021
LOG:  00000: todos los procesos fueron terminados; reinicializando
UBICACI�N:  reaper, postmaster.c:2209
DEBUG:  00000: shmem_exit(0)
UBICACI�N:  shmem_exit, ipc.c:126
DEBUG:  00000: invoking IpcMemoryCreate(size=110387200)
UBICACI�N:  CreateSharedMemoryAndSemaphores, ipci.c:99
LOG:  00000: el sistema de bases de datos fue interrumpido en 2006-09-04 13:40:56 CEST
UBICACI�N:  StartupXLOG, xlog.c:4373
LOG:  00000: el registro de checkpoint est� en 1/8C1A12A8
UBICACI�N:  StartupXLOG, xlog.c:4441
LOG:  00000: registro de redo en 1/8C1A12A8; registro de undo en 0/0; apagado FALSE
UBICACI�N:  StartupXLOG, xlog.c:4468
LOG:  00000: siguiente ID de transacci�n: 273407288; siguiente OID: 11724975
UBICACI�N:  StartupXLOG, xlog.c:4471
LOG:  00000: siguiente MultiXactId: 5; siguiente MultiXactOffset: 10
UBICACI�N:  StartupXLOG, xlog.c:4474
LOG:  00000: el sistema de bases de datos no fue apagado apropiadamente; se est� efectuando la recuperaci�n autom�tica
UBICACI�N:  StartupXLOG, xlog.c:4531
LOG:  00000: redo comienza en 1/8C1A12EC
UBICACI�N:  StartupXLOG, xlog.c:4568
LOG:  00000: conexi�n recibida: host=[local]
UBICACI�N:  BackendRun, postmaster.c:2699
DEBUG:  00000: forked new backend, pid=32029 socket=6
UBICACI�N:  BackendStartup, postmaster.c:2520
FATAL:  57P03: el sistema de base de datos est� inici�ndose
UBICACI�N:  ProcessStartupPacket, postmaster.c:1589
DEBUG:  00000: proc_exit(0)
UBICACI�N:  proc_exit, ipc.c:95
DEBUG:  00000: shmem_exit(0)
UBICACI�N:  shmem_exit, ipc.c:126
DEBUG:  00000: exit(0)
UBICACI�N:  proc_exit, ipc.c:113
DEBUG:  00000: reaping dead processes
UBICACI�N:  reaper, postmaster.c:2021
DEBUG:  00000: proceso de servidor (PID 32029) termin� con c�digo de salida 0
UBICACI�N:  LogChildExit, postmaster.c:2419
LOG:  00000: registro de longitud cero en 1/8E845664
UBICACI�N:  ReadRecord, xlog.c:2763
LOG:  00000: redo listo en 1/8E84563C
UBICACI�N:  StartupXLOG, xlog.c:4626
LOG:  00000: conexi�n recibida: host=[local]
UBICACI�N:  BackendRun, postmaster.c:2699
DEBUG:  00000: forked new backend, pid=32032 socket=6
UBICACI�N:  BackendStartup, postmaster.c:2520
FATAL:  57P03: el sistema de base de datos est� inici�ndose
UBICACI�N:  ProcessStartupPacket, postmaster.c:1589
DEBUG:  00000: proc_exit(0)
UBICACI�N:  proc_exit, ipc.c:95
DEBUG:  00000: shmem_exit(0)
UBICACI�N:  shmem_exit, ipc.c:126
DEBUG:  00000: exit(0)
UBICACI�N:  proc_exit, ipc.c:113
DEBUG:  00000: reaping dead processes
UBICACI�N:  reaper, postmaster.c:2021
DEBUG:  00000: proceso de servidor (PID 32032) termin� con c�digo de salida 0
UBICACI�N:  LogChildExit, postmaster.c:2419
LOG:  00000: el sistema de bases de datos est� listo
UBICACI�N:  StartupXLOG, xlog.c:4820
LOG:  00000: el l�mite para el reciclaje de ID de transacciones es 2147484146, limitado por base de datos �postgres�
UBICACI�N:  SetTransactionIdLimit, varsup.c:234
DEBUG:  00000: proc_exit(0)
UBICACI�N:  proc_exit, ipc.c:95
DEBUG:  00000: shmem_exit(0)
UBICACI�N:  shmem_exit, ipc.c:126
DEBUG:  00000: exit(0)
UBICACI�N:  proc_exit, ipc.c:113
DEBUG:  00000: reaping dead processes
UBICACI�N:  reaper, postmaster.c:2021
LOG:  00000: conexi�n recibida: host=[local]
UBICACI�N:  BackendRun, postmaster.c:2699
LOG:  00000: conexi�n autorizada: usuario=postgres database=postgres
UBICACI�N:  BackendRun, postmaster.c:2769
DEBUG:  00000: postmaster child[32040]: starting with (
UBICACI�N:  BackendRun, postmaster.c:2847
DEBUG:  00000:     postgres
UBICACI�N:  BackendRun, postmaster.c:2850
DEBUG:  00000:     -v196608
UBICACI�N:  BackendRun, postmaster.c:2850
DEBUG:  00000:     -p
UBICACI�N:  BackendRun, postmaster.c:2850
DEBUG:  00000:     postgres
UBICACI�N:  BackendRun, postmaster.c:2850
DEBUG:  00000: )
UBICACI�N:  BackendRun, postmaster.c:2852
DEBUG:  00000: InitPostgres
UBICACI�N:  PostgresMain, postgres.c:2946
DEBUG:  00000: StartTransaction
UBICACI�N:  ShowTransactionState, xact.c:3930
UBICACI�N:  ShowTransactionStateRec, xact.c:3955
DEBUG:  00000: CommitTransaction

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PostgreSQL XID exceeded crash.
Next
From: Alvaro Herrera
Date:
Subject: Re: PostgreSQL XID exceeded crash.