| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jorge Solórzano <jorsol(at)gmail(dot)com> |
| Cc: | Vladimir Gordiychuk <folyga(at)gmail(dot)com>, Dave Cramer <davecramer(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-19 17:09:31 |
| Message-ID: | CA+TgmoaALndXLu+PEPf4Xj869cycpG_0m9c9r0JB40d1yw+CUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On Thu, Jan 19, 2017 at 12:01 PM, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
> Robert, the logs I get from postgres (at least the section that matters) is
> here:
> If you need something else just ask...
That shows that there is a crash, but there's no stack trace in there.
Someone needs to get a core dump and use "gdb" to get stack trace.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-01-19 17:13:08 | Re: [HACKERS] SEGFAULT in HEAD with replication |
| Previous Message | Dave Cramer | 2017-01-19 17:09:11 | Re: [JDBC] SEGFAULT in HEAD with replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-01-19 17:13:08 | Re: [HACKERS] SEGFAULT in HEAD with replication |
| Previous Message | Dave Cramer | 2017-01-19 17:09:11 | Re: [JDBC] SEGFAULT in HEAD with replication |