Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication
Date
Msg-id 8164.1484863037@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication  (Jorge Solórzano <jorsol@gmail.com>)
Responses Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication  (Jorge Solórzano <jorsol@gmail.com>)
Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] SEGFAULT in HEAD with replication  (Jorge Solórzano <jorsol@gmail.com>)
Re: [HACKERS] SEGFAULT in HEAD with replication  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
=?UTF-8?Q?Jorge_Sol=C3=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.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Improving RLS planning
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical Replication WIP