Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-12-02 Thread Barry Lind
] Strange server error with current 8.0beta driver Oliver Jowett <[EMAIL PROTECTED]> writes: >> Perhaps PerformCursorOpen should copy the query tree before planning, >> or plan in a different memory context? > Patch attached. It moves query planning inside the new porta

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-28 Thread Tom Lane
Oliver Jowett <[EMAIL PROTECTED]> writes: >> Perhaps PerformCursorOpen should copy the query tree before planning, or >> plan in a different memory context? > Patch attached. It moves query planning inside the new portal's memory > context. With this applied I can run Barry's testcase without er

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-24 Thread Barry Lind
Cc: Tom Lane; [EMAIL PROTECTED] Subject: Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver Oliver Jowett wrote: > Perhaps PerformCursorOpen should copy the query tree before planning, > or plan in a different memory context? Patch attached. It moves query planning insi

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-24 Thread Oliver Jowett
Oliver Jowett wrote: Perhaps PerformCursorOpen should copy the query tree before planning, or plan in a different memory context? Patch attached. It moves query planning inside the new portal's memory context. With this applied I can run Barry's testcase without errors, and valgrind seems OK wit

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-24 Thread Oliver Jowett
Barry Lind wrote: I also have the test case (in java) down to the bare minimum that generated the following output (that test case is attached). (Note that if the FETCH in the test case is not executed then the backend crashes; with the FETCH you get an error: "ERROR: unrecognized node type: 0") I

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-23 Thread Barry Lind
ERROR: unrecognized node type: 0 Location: File: clauses.c, Routine: expression_tree_mutator, Line: 3220 Server SQLState: XX000 -----Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 7:10 AM To: Barry Lind Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subje

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-23 Thread Tom Lane
"Barry Lind" <[EMAIL PROTECTED]> writes: > OK, getting closer. The error happens if in jdbc I reuse > PreparedStatement objects to reexecute the same set of queries multiple > times. The TRAP you showed looked like it might have something to do with trying to execute code outside any transaction.

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-22 Thread Barry Lind
up what I have been working on. Thanks, --Barry -Original Message- From: Barry Lind Sent: Monday, November 22, 2004 7:48 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: FW: [HACKERS] [JDBC] Strange server error with current 8.0beta driver I have been unable to come up with a simpl

FW: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-22 Thread Barry Lind
ase it might mean anything to anyone. Thanks, --Barry -Original Message- From: Barry Lind Sent: Friday, November 19, 2004 5:40 PM To: Kris Jurka Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver Kris, Environment

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-20 Thread Oliver Jowett
Barry Lind wrote: Environment #1: WinXP 8.0beta4 server, 8.0jdbc client 2004-11-19 12:19:06 ERROR: unrecognized node type: 25344832 Environment #2: Sun Solaris 7.4.3 server, 8.0jdbc client ERROR: no value found for parameter 1 From memory the 7.4.3 behaviour you see can happen if you DECLARE C

Re: [HACKERS] [JDBC] Strange server error with current 8.0beta driver

2004-11-19 Thread Barry Lind
Kris, Environment #1: WinXP 8.0beta4 server, 8.0jdbc client I get random failures with the following errors: $ grep ERROR postgresql-2004-11-19_091524.log 2004-11-19 12:19:06 ERROR: unrecognized node type: 25344832 2004-11-19 12:20:06 ERROR: unrecognized node type: 25344832 2004-11-19 12:21:0