Re: Segmentation Fault in logical decoding get/peek API - Mailing list pgsql-bugs

From Jeremy Finzel
Subject Re: Segmentation Fault in logical decoding get/peek API
Date
Msg-id CAMa1XUgC8WrsSSBj_C6W3J+EC5PTnPEB+jNf4wzmDLT0xywWSw@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation Fault in logical decoding get/peek API  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
The best thing which could be done is to post a set of SQL queries
on this list which allows to reproduce the problem.

I am trying, but I am not sure how to do that just yet.  However, I can reliably reproduce the error by letting this system run, meaning I have the ability to attach a debugger to see what is happening more deeply.  I can also provide just what data in the slot is leading to a failed assert.  Would any of this help to narrow down the problem?

Thanks,
Jeremy

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15645: \COPY command not printing output in batch mode
Next
From: "Daniel Verite"
Date:
Subject: Re: BUG #15645: \COPY command not printing output in batch mode