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

2009-12-09 Thread Robert Haas
On Tue, Dec 8, 2009 at 11:08 PM, Tom Lane t...@sss.pgh.pa.us wrote: 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;

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

2009-12-09 Thread Andrew Gierth
Robert == Robert Haas robertmh...@gmail.com writes: Robert How about (3) getrlimit(RLIMIT_STACK) lies through its teeth, Robert by ignoring the existence of another and lower limit imposed Robert elsewhere? Robert A little Googling seems to reveal that FreeBSD has a Robert parameter called

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

2009-12-09 Thread Andrew Gierth
Oleg == Oleg Jurtšenko o...@fts.ee writes: Oleg I tried to execute select instr(ad_parent_tree(?,?),'|'||'?'||'|') AS Oleg isItsOwnChild from dual; query with psql terminal and got Oleg segmentation fault as well. Oleg The most interesting thing is that this function makes segmentation

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

2009-12-09 Thread Oleg Jurtšenko
Functions are attached Oleg Andrew Gierth wrote: Oleg == Oleg Jurtšenko o...@fts.ee writes: Oleg I tried to execute select instr(ad_parent_tree(?,?),'|'||'?'||'|') AS Oleg isItsOwnChild from dual; query with psql terminal and got Oleg segmentation fault as well. Oleg The

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

2009-12-09 Thread Stefan Kaltenbrunner
Andrew Gierth wrote: Robert == Robert Haas robertmh...@gmail.com writes: Robert How about (3) getrlimit(RLIMIT_STACK) lies through its teeth, Robert by ignoring the existence of another and lower limit imposed Robert elsewhere? Robert A little Googling seems to reveal that FreeBSD has a

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

2009-12-09 Thread Tom Lane
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes: I vaguely recall issues in the past with linking of postgresql (or PLs that require it) against libc_r causing some rather small stack limits being imposed under some circumstances but I don't recall the details any more... Yeah, we've

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

2009-12-09 Thread Andrew Gierth
Andrew == Andrew Gierth and...@tao11.riddles.org.uk writes: Andrew What are the definitions of your instr() and ad_parent_tree() Andrew functions? Well, there's so much wrong with that ad_parent_tree function - it's always going to recurse infinitely (with a new subxact per recursion level,

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

2009-12-09 Thread Tom Lane
Andrew Gierth and...@tao11.riddles.org.uk writes: Still, even though the code is preposterous, the result shouldn't be a segfault. I wasn't able to reproduce one myself (using 8.3.7 on freebsd 7.2) however. Yeah, for me it also recurses till the exception is hit, and then processes that

[BUGS] getting libpqd.lib and libpqd.dll for postgesql 8.4.1 on Vista with VS8 or cygwin g++

2009-12-09 Thread Mike Landis
I am trying to experiment with the libpqxx API and postgresql 8.4.1 on a 32-bit Vista machine. Libpqxx wants release and debug libraries for libpq available. libpq.dll ships with the binary release of PG and libpq.lib ships with the source tree, but debug versions have to be built from source.

[BUGS] BUG #5237: strange int-bit and bit-int conversions

2009-12-09 Thread Roman Kononov
The following bug has been logged online: Bug reference: 5237 Logged by: Roman Kononov Email address: kono...@ftml.net PostgreSQL version: 8.4.1 Operating system: GNU/Linux x86_64 Description:strange int-bit and bit-int conversions Details: test=# select

Re: [BUGS] BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly

2009-12-09 Thread Tom Lane
Robert Haas robertmh...@gmail.com writes: I'm not an expert on this area of the code, but can we just ignore isNatural and usingClause when deparsing? No. These properties are *not* ignorable because doing so changes the set of returned columns --- you should get only one column out not two.