Re: PostgreSQL XID exceeded crash.

Mario Lopez <mario@xxxxxxxxx> · Mon, 04 Sep 2006 18:02:54 +0200

Hi,

I forgot to mention that we are using plphp version 1.1 but I guess that 
in the process of making a pg_restore this issue does not really matter.

Thanks Mario.

Mario Lopez escribió:
Hi,

The platform as you have seen is Debian testing branch. I have 
activated log_statement but again nothing clear, the query that makes 
the system fail has nothing strange on it here is a dump.

I do not know how toget a stack trace and the "crash" does not provide 
a core dump :(. Could you explain how to obtain it?.

Thanks,

ID:8069 CMD_TAG:idle XID:274157580 DEBUG:  00000: StartTransaction
PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN:  ShowTransactionState, 
xact.c:3930
PID:8069 CMD_TAG:idle XID:274157580 DEBUG:  00000: name: unnamed; 
blockState:       DEFAULT; state: INPROGR, xid/subid/cid: 
274157580/1/0, nestlvl: 1, children: <>
PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN:  
ShowTransactionStateRec, xact.c:3955
PID:8069 CMD_TAG:idle XID:274157580 LOG:  00000: sentencia: INSERT 
INTO scannmap4 VALUES (1719913, 2, 117, 28, 1155, 17072, 1, 1, '', '', 
'', '', NULL);
PID:8069 CMD_TAG:idle XID:274157580 UBICACIÓN:  log_after_parse, 
postgres.c:605
PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG:  00000: ProcessQuery
PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN:  ProcessQuery, 
pquery.c:128
PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG:  00000: 
CommitTransactionCommand
PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN:  finish_xact_command, 
postgres.c:2006
PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG:  00000: CommitTransaction
PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN:  
ShowTransactionState, xact.c:3930
PID:8069 CMD_TAG:INSERT XID:274157580 DEBUG:  00000: name: unnamed; 
blockState:       STARTED; state: INPROGR, xid/subid/cid: 
274157580/1/0, nestlvl: 1, children: <>
PID:8069 CMD_TAG:INSERT XID:274157580 UBICACIÓN:  
ShowTransactionStateRec, xact.c:3955
PID:8069 CMD_TAG:INSERT XID:0 LOG:  00000: duración: 0.460 ms
PID:8069 CMD_TAG:INSERT XID:0 UBICACIÓN:  exec_simple_query, 
postgres.c:1090
PID:8069 CMD_TAG:idle XID:0 DEBUG:  00000: StartTransactionCommand
PID:8069 CMD_TAG:idle XID:0 UBICACIÓN:  start_xact_command, 
postgres.c:1983
PID:8069 CMD_TAG:idle XID:274157581 DEBUG:  00000: StartTransaction
PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN:  ShowTransactionState, 
xact.c:3930
PID:8069 CMD_TAG:idle XID:274157581 DEBUG:  00000: name: unnamed; 
blockState:       DEFAULT; state: INPROGR, xid/subid/cid: 
274157581/1/0, nestlvl: 1, children: <>
PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN:  
ShowTransactionStateRec, xact.c:3955
PID:8069 CMD_TAG:idle XID:274157581 LOG:  00000: sentencia: INSERT 
INTO scannmap4 VALUES (1719914, 2, 117, 28, 1155, 17073, 1, 1, '', '', 
'', '', NULL);
PID:8069 CMD_TAG:idle XID:274157581 UBICACIÓN:  log_after_parse, 
postgres.c:605
PID:8025 CMD_TAG: XID: DEBUG:  00000: reaping dead processes
PID:8025 CMD_TAG: XID: UBICACIÓN:  reaper, postmaster.c:2021
PID:8025 CMD_TAG: XID: DEBUG:  00000: proceso de servidor (PID 8069) 
terminó con código de salida 255
PID:8025 CMD_TAG: XID: UBICACIÓN:  LogChildExit, postmaster.c:2419
PID:8025 CMD_TAG: XID: LOG:  00000: proceso de servidor (PID 8069) 
terminó con código de salida 255
PID:8025 CMD_TAG: XID: UBICACIÓN:  LogChildExit, postmaster.c:2419
PID:8025 CMD_TAG: XID: LOG:  00000: terminando todos los otros 
procesos de servidor activos
PID:8025 CMD_TAG: XID: UBICACIÓN:  HandleChildCrash, postmaster.c:2309
PID:8025 CMD_TAG: XID: DEBUG:  00000: sending SIGQUIT to process 8028
PID:8025 CMD_TAG: XID: UBICACIÓN:  HandleChildCrash, postmaster.c:2362
PID:8025 CMD_TAG: XID: DEBUG:  00000: sending SIGQUIT to process 8029
PID:8025 CMD_TAG: XID: UBICACIÓN:  HandleChildCrash, postmaster.c:2396
PID:8025 CMD_TAG: XID: DEBUG:  00000: reaping dead processes
PID:8025 CMD_TAG: XID: UBICACIÓN:  reaper, postmaster.c:2021
PID:8025 CMD_TAG: XID: LOG:  00000: todos los procesos fueron 
terminados; reinicializando
PID:8025 CMD_TAG: XID: UBICACIÓN:  reaper, postmaster.c:2209
PID:8025 CMD_TAG: XID: DEBUG:  00000: shmem_exit(0)
PID:8025 CMD_TAG: XID: UBICACIÓN:  shmem_exit, ipc.c:126
PID:8025 CMD_TAG: XID: DEBUG:  00000: invoking 
IpcMemoryCreate(size=110387200)
PID:8025 CMD_TAG: XID: UBICACIÓN:  CreateSharedMemoryAndSemaphores, 
ipci.c:99
PID:8120 CMD_TAG: XID: LOG:  00000: el sistema de bases de datos fue 
interrumpido en 2006-09-04 18:56:21 CEST
PID:8120 CMD_TAG: XID: UBICACIÓN:  StartupXLOG, xlog.c:4373
PID:8120 CMD_TAG: XID: LOG:  00000: el registro de checkpoint está en 
1/93231A60
PID:8120 CMD_TAG: XID: UBICACIÓN:  StartupXLOG, xlog.c:4441
PID:8120 CMD_TAG: XID: LOG:  00000: registro de redo en 1/93231A60; 
registro de undo en 0/0; apagado TR

Tom Lane escribió:
Alvaro Herrera <alvherre@xxxxxxxxxxxxxxxxx> writes:

Maybe someone else has an idea?  The previous-to-last message below is
"server process exited with exit code 255".

That's very strange if the platform is Linux --- I was guessing it was
Windows.

Please try to get a core dump from the crash and provide a stack trace.

Another thing that would be useful is to turn on log_statement so we can
see the exact command causing the crash.

            regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster