Re: [HACKERS] SEGFAULT in HEAD with replication

From: Jorge Solórzano <jorsol(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, Vladimir Gordiychuk <folyga(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [HACKERS] SEGFAULT in HEAD with replication
Date: 2017-01-19 23:31:52
Message-ID: CA+cVU8NO5DM+VJvyVzRAxVfRQeLOwo3JNmLszkFQvW3n=KUGkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

Yes, in fact it's a totally empty string:
https://github.com/pgjdbc/pgjdbc/blob/master/pgjdbc/src/main/java/org/postgresql/jdbc/PgConnection.java#L1317

Jorge Solórzano
me.jorsol.com

On Thu, Jan 19, 2017 at 3:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> =?UTF-8?Q?Jorge_Sol=C3=B3rzano?= <jorsol(at)gmail(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-01-20 00:09:45 Re: [JDBC] SEGFAULT in HEAD with replication
Previous Message Tom Lane 2017-01-19 23:22:33 Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2017-01-20 00:09:45 Re: [JDBC] SEGFAULT in HEAD with replication
Previous Message Tom Lane 2017-01-19 21:57:17 Re: [HACKERS] SEGFAULT in HEAD with replication