"dolejsi jiri" writes:
> executing following query 2 times crashes postgres server:
The stack trace is
#0 0x003d7e42e989 in xmlCleanupCharEncodingHandlers ()
from /usr/lib64/libxml2.so.2
#1 0x003d7e437725 in xmlCleanupParser () from /usr/lib64/libxml2.so.2
#2 0x7fac004e270d in
"Mauro Infantino" writes:
> I'm just experiencing the same as in here,
> http://archives.postgresql.org/pgsql-bugs/2008-06/msg00175.php
> It was not happening for 8.3.7 (at least on Windows).
This is the very definition of an unhelpful bug report.
You are not seeing the same thing that was repor
On Thu, 17 Sep 2009, Joseph Shraibman wrote:
[when passing a multi-statement sql string to executeUpdate, if a
statement after the first is a select, it is silently not fully
executed.]
Running queries in executeUpdate is not allowed. If you pass a plain
select to executeUpdate it complai
"Stefan" writes:
> The problem is that if it is no record in the table, it seems that first the
> INSERT command is issued and after that the UPDATE command is issued, too.
Well, yeah. That's exactly how it's documented to work: an ON INSERT
rule is executed after the INSERT proper.
You could m
