| 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: [JDBC] SEGFAULT in HEAD with replication |
| Date: | 2017-01-20 00:09:45 |
| Message-ID: | 4858.1484870985@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-01-20 01:19:06 | Re: Patch to implement pg_current_logfile() function |
| Previous Message | Jorge Solórzano | 2017-01-19 23:31:52 | Re: [HACKERS] SEGFAULT in HEAD with replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jorge Solórzano | 2017-01-20 13:53:05 | Re: [JDBC] SEGFAULT in HEAD with replication |
| Previous Message | Jorge Solórzano | 2017-01-19 23:31:52 | Re: [HACKERS] SEGFAULT in HEAD with replication |