On Tue, Apr 14, 2020 at 9:14 PM Erik Rijkers <e...@xs4all.nl> wrote: > > On 2020-04-14 12:10, Dilip Kumar wrote: > > > v14-0001-Immediately-WAL-log-assignments.patch + > > v14-0002-Issue-individual-invalidations-with.patch + > > v14-0003-Extend-the-output-plugin-API-with-stream-methods.patch+ > > v14-0004-Gracefully-handle-concurrent-aborts-of-uncommitt.patch+ > > v14-0005-Implement-streaming-mode-in-ReorderBuffer.patch + > > v14-0006-Add-support-for-streaming-to-built-in-replicatio.patch+ > > v14-0007-Track-statistics-for-streaming.patch + > > v14-0008-Enable-streaming-for-all-subscription-TAP-tests.patch + > > v14-0009-Add-TAP-test-for-streaming-vs.-DDL.patch + > > v14-0010-Bugfix-handling-of-incomplete-toast-tuple.patch > > applied on top of 8128b0c (a few hours ago) > > Hi, > > I haven't followed this thread and maybe this instabilty is > known/expected; just thought I'd let you know. > > When doing running a pgbench run over logical replication (cascading > down two replicas), I get this segmentation fault.
Thanks for the testing. Is it possible to share the call stack? > > 2020-04-14 17:27:28.135 CEST [8118] DETAIL: Streaming transactions > committing after 0/5FA2A38, reading WAL from 0/5FA2A00. > 2020-04-14 17:27:28.135 CEST [8118] LOG: logical decoding found > consistent point at 0/5FA2A00 > 2020-04-14 17:27:28.135 CEST [8118] DETAIL: There are no running > transactions. > 2020-04-14 17:27:28.138 CEST [8006] LOG: server process (PID 8118) was > terminated by signal 11: Segmentation fault > 2020-04-14 17:27:28.138 CEST [8006] DETAIL: Failed process was running: > COMMIT > 2020-04-14 17:27:28.138 CEST [8006] LOG: terminating any other active > server processes > 2020-04-14 17:27:28.138 CEST [8163] WARNING: terminating connection > because of crash of another server process > 2020-04-14 17:27:28.138 CEST [8163] DETAIL: The postmaster has > commanded this server process to roll back the current transaction and > exit, because another server process exited abnormally and possibly > corrupted shared memory. > 2020-04-14 17:27:28.138 CEST [8163] HINT: In a moment you should be > able to reconnect to the database and repeat your command. > > > This error happens somewhat buried away in my test-stuff; I can dig it > out and make it into a repeatable test if you need it. (debian > stretch/gcc 9.3.0) Yeah, that will be great. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com