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

From Jorge Solórzano
Subject Re: [HACKERS] SEGFAULT in HEAD with replication
Date
Msg-id CA+cVU8PJs-W1vp-LumirHiYM1dA_OUwnkkDqRmqF6DJF3bLnCA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thanks tom, I confirm that ba61a04 fixes the issue. Now CI is passing.

Jorge Solórzano
me.jorsol.com

On Thu, Jan 19, 2017 at 6:09 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
I wrote:
> 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.

Oh, duh: the reason it's not trivial to reproduce is you have to try
to bind an empty prepared statement *in an already-aborted transaction*.

Will push a fix in a bit.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: [HACKERS] Improvements in psql hooks for variables
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Improvements in psql hooks for variables