| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jorge Solórzano <jorsol(at)gmail(dot)com> |
| 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 21:57:17 |
| Message-ID: | 8164.1484863037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
=?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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-01-19 22:01:39 | Re: Logical Replication WIP |
| Previous Message | Tom Lane | 2017-01-19 21:51:02 | Re: Improving RLS planning |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Solórzano | 2017-01-19 23:31:52 | Re: [HACKERS] SEGFAULT in HEAD with replication |
| Previous Message | Jorge Solórzano | 2017-01-19 21:31:57 | Re: [HACKERS] SEGFAULT in HEAD with replication |