Re:Re: Bug: ERROR: invalid cache ID: 42 CONTEXT: parallel worker - Mailing list pgsql-bugs
| From | jimmy |
|---|---|
| Subject | Re:Re: Bug: ERROR: invalid cache ID: 42 CONTEXT: parallel worker |
| Date | |
| Msg-id | 6294a60f.3289.1655f8e02f6.Coremail.mpokky@126.com Whole thread Raw |
| In response to | Re: Bug: ERROR: invalid cache ID: 42 CONTEXT: parallel worker (Tom Lane <tgl@sss.pgh.pa.us>) |
| Responses |
Re: Re: Bug: ERROR: invalid cache ID: 42 CONTEXT: parallel worker
(Thomas Munro <thomas.munro@enterprisedb.com>)
|
| List | pgsql-bugs |
This is the debug log below. Is it useful. Thank you.
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x0000000000828ed7 in hash_search_with_hash_value ()
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x0000000000828ed7 in hash_search_with_hash_value ()
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x00000000006f16e3 in ?? ()
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x00000000006f16e3 in ?? ()
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
Continuing.
Program received signal SIGUSR1, User defined signal 1.
0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
#0 0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1 0x00000000006fd685 in WaitEventSetWait ()
#2 0x00000000006fdee9 in WaitLatchOrSocket ()
#3 0x00000000006a56c8 in WaitForBackgroundWorkerShutdown ()
#4 0x00000000004de17e in ?? ()
#5 0x00000000004de2a8 in DestroyParallelContext ()
#6 0x00000000004de343 in AtEOXact_Parallel ()
#7 0x00000000004e7597 in ?? ()
#8 0x00000000004e7be5 in AbortCurrentTransaction ()
#9 0x000000000072023d in PostgresMain ()
#10 0x00000000006b498a in PostmasterMain ()
#11 0x0000000000635720 in main ()
#0 0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1 0x00000000006fd685 in WaitEventSetWait ()
#2 0x00000000006fdee9 in WaitLatchOrSocket ()
#3 0x00000000006a56c8 in WaitForBackgroundWorkerShutdown ()
#4 0x00000000004de17e in ?? ()
#5 0x00000000004de2a8 in DestroyParallelContext ()
#6 0x00000000004de343 in AtEOXact_Parallel ()
#7 0x00000000004e7597 in ?? ()
#8 0x00000000004e7be5 in AbortCurrentTransaction ()
#9 0x000000000072023d in PostgresMain ()
#10 0x00000000006b498a in PostmasterMain ()
#11 0x0000000000635720 in main ()
Continuing.
Program received signal SIGINT, Interrupt.
0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
#0 0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1 0x00000000006fd685 in WaitEventSetWait ()
#2 0x00000000006253e6 in secure_read ()
#3 0x000000000062fddb in ?? ()
#4 0x00000000006301eb in pq_getbyte ()
#5 0x000000000071f9d0 in PostgresMain ()
#6 0x00000000006b498a in PostmasterMain ()
#7 0x0000000000635720 in main ()
#0 0x00000035848e8853 in __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1 0x00000000006fd685 in WaitEventSetWait ()
#2 0x00000000006253e6 in secure_read ()
#3 0x000000000062fddb in ?? ()
#4 0x00000000006301eb in pq_getbyte ()
#5 0x000000000071f9d0 in PostgresMain ()
#6 0x00000000006b498a in PostmasterMain ()
#7 0x0000000000635720 in main ()
At 2018-08-17 21:28:17, "Tom Lane" <tgl@sss.pgh.pa.us> wrote: >jimmy <mpokky@126.com> writes: >> ERROR: invalid cache ID: 42 >> CONTEXT: parallel worker > >We had a similar report back in April: > >https://www.postgresql.org/message-id/flat/152337570402.31228.237601111670899842%40wrigleys.postgresql.org > >but that didn't have enough information to debug the problem, and >neither does this. Can you provide a *self contained* test case, >or failing that, do some debugging of your own as suggested in the >previous thread? > >https://wiki.postgresql.org/wiki/Guide_to_reporting_problems > > regards, tom lane
pgsql-bugs by date: