On Thu, Jan 19, 2017 at 3:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Jorge Sol\xC3=B3rzano <jorsol@gmail.com> writes: > After many tries I get this: > #0 0x0000000000836950 in exec_bind_message (input_message=0x7ffce81048a0) > at postgres.c:1562
Hmm ... that line was last touched by ab1f0c822, so I'm betting that I broke it somehow, but I'm not sure how.
It looks like S_3 might have been parsed from a totally empty source string? But if that's the trigger, I'd think it'd be entirely trivial to reproduce.