Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-20 Thread Jorge Solórzano
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 wrote: > I wrote: > > Hmm ... that line was last touched by ab1f0

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Tom Lane
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 r

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Jorge Solórzano
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 wrote: > =?UTF-8?Q?Jorge_Sol=C3=B3rzano?= writes: > > After many tries

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Tom Lane
=?UTF-8?Q?Jorge_Sol=C3=B3rzano?= writes: > After many tries I get this: > #0 0x00836950 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

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Jorge Solórzano
After many tries I get this: #0 0x00836950 in exec_bind_message (input_message=0x7ffce81048a0) at postgres.c:1562 #1 0x0083a23d in PostgresMain (argc=1, argv=0x2bd93d8, dbname=0x2bd9130 "test", username=0x2bd9110 "test") at postgres.c:4113 #2 0x007aacd4 in BackendRun (po

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Dave Cramer
Not sure you can get the exec. We are working on producing the BT from Travis-CI or I will build and run the test locally and get the trace Dave Cramer On 19 January 2017 at 15:31, Craig Ringer wrote: > > > On 20 Jan. 2017 04:13, "Robert Haas" wrote: > > On Thu, Jan 19, 2017 at 12:09 PM, Dave

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Craig Ringer
On 20 Jan. 2017 04:13, "Robert Haas" wrote: On Thu, Jan 19, 2017 at 12:09 PM, Dave Cramer wrote: > I would have expected more, but this is what I have > > bt full > #0 InitPredicateLocks () at predicate.c:1250 > i = > info = {num_partitions = 1, ssize = 140731424825288, dsize

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Robert Haas
On Thu, Jan 19, 2017 at 12:09 PM, Dave Cramer wrote: > I would have expected more, but this is what I have > > bt full > #0 InitPredicateLocks () at predicate.c:1250 > i = > info = {num_partitions = 1, ssize = 140731424825288, dsize = 1, > max_dsize = 0, ffactor = 1407

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Dave Cramer
I would have expected more, but this is what I have bt full #0 InitPredicateLocks () at predicate.c:1250 i = info = {num_partitions = 1, ssize = 140731424825288, dsize = 1, max_dsize = 0, ffactor = 140731424836952, keysize = 140356326474085, entrysize = 14072

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Robert Haas
On Thu, Jan 19, 2017 at 12:01 PM, Jorge Solórzano 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 "

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Dave Cramer
I'll try to get the stack trace from the core dump, have to build master first Dave Cramer On 19 January 2017 at 12:01, Jorge Solórzano wrote: > Robert, the logs I get from postgres (at least the section that matters) > is here: > If you need something else just ask... > > 2017-01-19 08:54:57.3

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Jorge Solórzano
Robert, the logs I get from postgres (at least the section that matters) is here: If you need something else just ask... 2017-01-19 08:54:57.319 CST [31734] DEBUG: CommitTransaction(1) name: > unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0 > 2017-01-19 08:54:57.321 CST [31734]

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Robert Haas
On Thu, Jan 19, 2017 at 10:59 AM, Jorge Solórzano wrote: > I have isolated the tests run by the pgjdbc project, I have disabled the > replication (wal_level = minimal) and the error is still present so it seems > that this error is not related to the replication, the test that cause the > error is

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Jorge Solórzano
I have isolated the tests run by the pgjdbc project, I have disabled the replication (wal_level = minimal) and the error is still present so it seems that this error is not related to the replication, the test that cause the error is AutoRollbackTestSuite, I have enable DEBUG mesages in postgresql

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Vladimir Gordiychuk
Core dump was extracted from this build https://travis-ci.org/Gordiychuk/pgjdbc/builds/193318018 2017-01-19 17:38 GMT+03:00 Vladimir Gordiychuk : > Last success build from postgresql HEAD was 20 days ago > https://travis-ci.org/pgjdbc/pgjdbc/builds/187764274 > We detect this problem 3 days ago.

Re: [HACKERS] [JDBC] SEGFAULT in HEAD with replication

2017-01-19 Thread Vladimir Gordiychuk
Last success build from postgresql HEAD was 20 days ago https://travis-ci.org/pgjdbc/pgjdbc/builds/187764274 We detect this problem 3 days ago. 2017-01-19 17:22 GMT+03:00 Dave Cramer : > The travis job https://travis-ci.org/pgjdbc/pgjdbc/jobs/192517342 is > seeing a segfault when we are testing a