Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Craig Ringer
On 8/12/2009 8:09 AM, Tom Lane wrote: Oleg Yurchenkoo...@fts.ee writes: Program terminated with signal 11, Segmentation fault. #0 0x0839380b in MemoryContextAllocZeroAligned (context=0x2d9eaf70, size=16) at mcxt.c:559 559 mcxt.c: No such file or directory. in mcxt.c [New Thread

Re: [BUGS] BUG #5099: When MetaData is acquired, it becomes an SQL error.

2009-12-08 Thread Hiroshi Saito
Hi Kris-san. Great, thanks!! You have spent very much time for this problem. I think very many Postgres users was helped by it. Thanks again:-) Regards, Hiroshi Saito - Original Message - From: Kris Jurka bo...@ejurka.com On Wed, 7 Oct 2009, konishi wrote: Bug reference:

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Oleg Jurtšenko
This the end of core dump. It is 8.3M bzip-ed. I can provide it on the request. I'm trying to compile Openbravo ERP application. There is no C/Perl/Python functions. My investigations show that pgsql catches segmentation fault on some| ||ported Oracle PLSQL function|: Query in the source code

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Robert Haas
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: This the end of core dump. It is 8.3M bzip-ed. I can provide it on the request. I think maybe the beginning would be more useful than the end. ...Robert -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Oleg Jurtšenko
Both files are there. Oleg. Robert Haas wrote: 2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: This the end of core dump. It is 8.3M bzip-ed. I can provide it on the request. I think maybe the beginning would be more useful than the end. ...Robert -- Sent via pgsql-bugs

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Oleg Jurtšenko
Once more: http://www.fts.ee/pgsqldebug.tgz - with loging enabled http://www.ftse.ee/pg_core.tar.bzip2 - full core dump Robert Haas wrote: 2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: Both files are there. Both files are where? I don't see an attachment or a

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Robert Haas
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: Once more: http://www.fts.ee/pgsqldebug.tgz - with loging enabled http://www.ftse.ee/pg_core.tar.bzip2 - full core dump It looks like you've got a pl/pgsql function that called itself recursively 1417 times before running out of stack space.

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Oleg Jurtšenko
You are right, it crushes on following statement: select instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual; max_stack_depth is commented out, I think it has the default value: #max_stack_depth = 2MB I'm attaching related functions. Oleg Robert Haas wrote: 2009/12/8 Oleg

[BUGS] BUG #5236: Aparent bug in ecpg

2009-12-08 Thread Marcelo Mas
The following bug has been logged online: Bug reference: 5236 Logged by: Marcelo Mas Email address: m...@atg.com.uy PostgreSQL version: 8.4.1 Operating system: Suse 10 Description:Aparent bug in ecpg Details: At the company I work we developed a database adapter in

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Robert Haas
2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: You are right, it crushes on following statement: select instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual; max_stack_depth is commented out, I think it has the default value: #max_stack_depth = 2MB Well, my guess is you have

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Tom Lane
Robert Haas robertmh...@gmail.com writes: 2009/12/8 Oleg Jurtšenko oleg.jurtse...@fts.ee: You are right, it crushes on following statement: select instr(ad_parent_tree(?,?),'|'||?||'|') AS isItsOwnChild from dual; max_stack_depth is commented out, I think it has the default value:

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Craig Ringer
(resending with list cc'd) Oleg Jurtšenko wrote: Core dump file are available here: www.fts.ee/pgsqldebug.tgz - with loging enabled Well, it certainly looks recursive: #0 0x0839380b in MemoryContextAllocZeroAligned (context=0x2d9eaf70, size=16) at mcxt.c:559 #1 0x081bfc16 in

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Craig Ringer
Recursion within PL/PgSQL? er ... sorry for stating the belated and obvious. I was dropped from the CC on the other branch of this thread so it wasn't hitting my INBOX and didn't realise it'd carried on until I saw it in my Pg list folder. -- Craig Ringer -- Sent via pgsql-bugs mailing list

Re: [BUGS] BUG #5235: Segmentation fault under high load through JDBC

2009-12-08 Thread Oleg Jurtšenko
I'm not sure about the theory about recursion and infinity loop. I have tested different versions of Postgres and FreeBSD. Please take a look on results below. Well, output of ulimit -a: $ ulimit -a cpu time (seconds, -t) unlimited file size (512-blocks, -f)