| Lists: | pgsql-jdbc |
|---|
| From: | "Barry Lind" <blind(at)xythos(dot)com> |
|---|---|
| To: | <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Strange server error with current 8.0beta driver |
| Date: | 2004-11-19 20:40:15 |
| Message-ID: | 03E7D3E231BB7B4A915A6581D4296CC6C08B24@NSNOVPS00411.nacio.xythos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
During my testing with the 8.0 driver, I am occasionally getting
failures. The strange thing is that a test will only fail 1 out of 10
times. The error I am getting from the server is:
ERROR: unrecognized node type: 25344832
(the number in the message varies). Does anyone know what this server
error means? I don't have the server source code installed right now to
look it up.
Also, I don't see these errors with the 7.4 driver. So I suspect
something in the V3 protocol path is triggering this error.
Thanks,
--Barry
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Barry Lind <blind(at)xythos(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Strange server error with current 8.0beta driver |
| Date: | 2004-11-19 23:57:27 |
| Message-ID: | Pine.BSO.4.56.0411191849080.25486@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
On Fri, 19 Nov 2004, Barry Lind wrote:
> During my testing with the 8.0 driver, I am occasionally getting
> failures. The strange thing is that a test will only fail 1 out of 10
> times. The error I am getting from the server is:
>
> ERROR: unrecognized node type: 25344832
This type of error points to a bug in the server. It means a query plan
is created that it can't process. A higher level node finds a lower level
node that it doesn't expect. The variability of the test failure could be
due to different plans being generated (note that V2 vs V3 can generate
different plans because of string substitution vs a prepared query). The
fact that the node number varies is a little suspicious, also because it's
a very large value. Does it vary between a couple values or is it
different every time. If it varies wildly then that could point to a
memory overwrite instead of a bad plan being created, but in any case this
problem is on the server side.
Kris Jurka
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Strange server error with current 8.0beta driver |
| Date: | 2004-11-20 01:28:55 |
| Message-ID: | 694.1100914135@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
Kris Jurka <books(at)ejurka(dot)com> writes:
> On Fri, 19 Nov 2004, Barry Lind wrote:
>> ERROR: unrecognized node type: 25344832
> This type of error points to a bug in the server.
Right. Could we see a test case?
If you did not build the server with --enable-cassert, try doing so;
that will probably make the error more reproducible. I suspect that
you've found a problem with dangling pointers or some such, and the
variability depends on whether the referenced memory has been re-used
yet. --enable-cassert turns on code to wipe freed memory immediately,
so it should make it easier to track down the query that causes this.
regards, tom lane