Re: Segfault logical replication PG 10.4

Поиск
Список
Период
Сортировка
От Mai Peng
Тема Re: Segfault logical replication PG 10.4
Дата
Msg-id ABAE13A9-4848-4354-A4B0-9F7286B999CF@webedia-group.com
обсуждение исходный текст
Ответ на Re: Segfault logical replication PG 10.4  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Segfault logical replication PG 10.4  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hello,
Here the backtrace

```Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `postgres: bgworker: logical replication worker for subscription'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  GetActiveSnapshot () at ./build/../src/backend/utils/time/snapmgr.c:843
843     ./build/../src/backend/utils/time/snapmgr.c: No such file or directory.
(gdb) up
#1  0x000056239fc83ecd in postquel_start (fcache=0x5623a1c83b78, es=0x5623a1c91a70)
    at ./build/../src/backend/executor/functions.c:809
809     ./build/../src/backend/executor/functions.c: No such file or directory.
(gdb) up
#2  fmgr_sql (fcinfo=0x5623a1c7af98) at ./build/../src/backend/executor/functions.c:1150
1150    in ./build/../src/backend/executor/functions.c
(gdb) up
#3  0x000056239fc75b4f in ExecInterpExpr (state=0x5623a1c7aeb8, econtext=0x5623a1c7b898, isnull=<optimized out>)
    at ./build/../src/backend/executor/execExprInterp.c:672
672     ./build/../src/backend/executor/execExprInterp.c: No such file or directory.
(gdb) up
#4  0x000056239fc72a96 in ExecEvalExprSwitchContext (isNull=0x7ffdc20d1487 "", econtext=0x5623a1c7b898,
    state=<optimized out>) at ./build/../src/include/executor/executor.h:308
308     ./build/../src/include/executor/executor.h: No such file or directory.
(gdb) up
#5  ExecCheck (state=<optimized out>, econtext=econtext@entry=0x5623a1c7b898)
    at ./build/../src/backend/executor/execExpr.c:556
556     ./build/../src/backend/executor/execExpr.c: No such file or directory.
(gdb) up
#6  0x000056239fdefec0 in domain_check_input (value=value@entry=94711038065448, isnull=0 '\000',
    my_extra=my_extra@entry=0x5623a1c79bd0) at ./build/../src/backend/utils/adt/domains.c:180
180     ./build/../src/backend/utils/adt/domains.c: No such file or directory.
(gdb) up
#7  0x000056239fdf0100 in domain_in (fcinfo=0x7ffdc20d1530) at ./build/../src/backend/utils/adt/domains.c:255
255     in ./build/../src/backend/utils/adt/domains.c
(gdb) up
#8  0x000056239feccd85 in InputFunctionCall (flinfo=flinfo@entry=0x7ffdc20d1900,
    str=str@entry=0x5623a1bf4698 "{test.Type.blabla}", typioparam=typioparam@entry=28498, typmod=typmod@entry=-1) at
./build/../src/backend/utils/fmgr/fmgr.c:1640
1640    ./build/../src/backend/utils/fmgr/fmgr.c: No such file or directory.
(gdb) up
#9  0x000056239fecd01d in OidInputFunctionCall (functionId=<optimized out>,
    str=0x5623a1bf4698 "{test.Type.blabla}",
    typioparam=28498, typmod=-1) at ./build/../src/backend/utils/fmgr/fmgr.c:1743
1743    in ./build/../src/backend/utils/fmgr/fmgr.c
(gdb) up
#10 0x000056239fd6429f in slot_store_cstrings (slot=slot@entry=0x5623a1c664e8, rel=rel@entry=0x5623a1c60bf0,
    values=values@entry=0x7ffdc20d1a70) at ./build/../src/backend/replication/logical/worker.c:354
354     ./build/../src/backend/replication/logical/worker.c: No such file or directory.
(gdb) up
#11 0x000056239fd64cc2 in apply_handle_insert (s=s@entry=0x7ffdc20d5580)
    at ./build/../src/backend/replication/logical/worker.c:612
612     in ./build/../src/backend/replication/logical/worker.c
(gdb) up
#12 0x000056239fd65e5b in apply_dispatch (s=0x7ffdc20d5580) at ./build/../src/backend/replication/logical/worker.c:912
912     in ./build/../src/backend/replication/logical/worker.c
(gdb) up
#13 LogicalRepApplyLoop (last_received=97628639619392) at ./build/../src/backend/replication/logical/worker.c:1119
1119    in ./build/../src/backend/replication/logical/worker.c
(gdb) up
#14 ApplyWorkerMain (main_arg=<optimized out>) at ./build/../src/backend/replication/logical/worker.c:1671
1671    in ./build/../src/backend/replication/logical/worker.c
(gdb) up
#15 0x000056239fd3540c in StartBackgroundWorker () at ./build/../src/backend/postmaster/bgworker.c:835
835     ./build/../src/backend/postmaster/bgworker.c: No such file or directory.
(gdb) up
#16 0x000056239fd42175 in do_start_bgworker (rw=0x5623a1b71870) at ./build/../src/backend/postmaster/postmaster.c:5728
5728    ./build/../src/backend/postmaster/postmaster.c: No such file or directory.
(gdb) up
#17 maybe_start_bgworkers () at ./build/../src/backend/postmaster/postmaster.c:5941
5941    in ./build/../src/backend/postmaster/postmaster.c
(gdb) up
#18 0x000056239fd42d35 in sigusr1_handler (postgres_signal_arg=<optimized out>)
    at ./build/../src/backend/postmaster/postmaster.c:5121
5121    in ./build/../src/backend/postmaster/postmaster.c
(gdb) up
#19 <signal handler called>
(gdb) up
#20 0x00007f533261a3a3 in __select_nocancel () at ../sysdeps/unix/syscall-template.S:84
84      ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) up
#21 0x000056239fae8c71 in ServerLoop () at ./build/../src/backend/postmaster/postmaster.c:1719
1719    ./build/../src/backend/postmaster/postmaster.c: No such file or directory.
(gdb) up
#22 0x000056239fd4407a in PostmasterMain (argc=3, argv=0x5623a1b49ef0)
    at ./build/../src/backend/postmaster/postmaster.c:1363
1363    in ./build/../src/backend/postmaster/postmaster.c
(gdb) up
#23 0x000056239faeac74 in main (argc=3, argv=0x5623a1b49ef0) at ./build/../src/backend/main/main.c:228
228     ./build/../src/backend/main/main.c: No such file or directory.```

BR

> Le 14 juil. 2018 à 13:15, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> a écrit :
>
> On 12.07.18 00:56, Mai Peng wrote:
>> We discovered our pg_wal partition was full few days after setting our
>> first logical publication on a PG 10.4 instance.
>> Then, we can not synchronise our slave to the master, it triggers a
>> segfault on the slave. We had to drop manually the subscription on slave
>> and the slot on master.
>> Then, we wanted to find the cause of this bug, stop connection between
>> master and slave , after 30 minutes, the slave had a segfault and could
>> not synchronise.
>> Why does the slave can not synchronise without a complete creation
>> subscription after dropping the slot?
>
> Can you get a backtrace from the core dump produced by the segfault?
>
> --
> Peter Eisentraut              http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ENOSPC FailedAssertion("!(RefCountErrors == 0)"
Следующее
От: Jesper Pedersen
Дата:
Сообщение: Re: partition tree inspection functions