| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Ondřej Jirman <ienieghapheoghaiwida(at)xff(dot)cz> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker |
| Date: | 2019-11-21 13:37:14 |
| Message-ID: | 20191121133714.dezdkhqjuzejoegb@development |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Nov 21, 2019 at 02:12:02PM +0100, Ondřej Jirman wrote:
>On Thu, Nov 21, 2019 at 01:59:30PM +0100, Tomas Vondra wrote:
>> On Thu, Nov 21, 2019 at 12:53:26PM +0100, Ondřej Jirman wrote:
>> >
>> > ...
>> >
>> OK, so this is the problematic table. Any idea what operation triggers
>> the issue? Having a small reproducer (say, a single-row insert or so)
>> would be very helpful.
>
>Can something be extracted from the logical decoding data I sent in the other
>e-mail? That seems to contain the failing operation, but I don't know how to
>decode it off the top of my head from that binary representation.
>
Well, why not use pg_logical_slot_peek_changes()? That should be human
readable, I think.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondřej Jirman | 2019-11-21 13:46:45 | Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker |
| Previous Message | Tomas Vondra | 2019-11-21 13:32:37 | Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker |