Re: Oracle vs PostgreSQL in real life - Mailing list pgsql-hackers

From Antonio Sergio de Mello e Souza
Subject Re: Oracle vs PostgreSQL in real life
Date
Msg-id 3C7E7475.4060602@bol.com.br
Whole thread Raw
In response to Oracle vs PostgreSQL in real life  (Jean-Paul ARGUDO <jean-paul.argudo@idealx.com>)
Responses Re: Oracle vs PostgreSQL in real life  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
  Jean-Paul ARGUDO wrote:

>As I wrote it before there, it is an ECPG script that runs with bad perfs.
>I put back trace/ notices/debug mode on the server.
>
>Here is an example of what does the debug doesnt stop to do:
>
>c... stuffs are CURSORS
>
>it seems that on every commit, the cursor is closed
>
>[... snip ...]
>NOTICE:  Closing pre-existing portal "csearcht04"
>
...

>NOTICE:  Closing pre-existing portal "cfindplu"
>NOTICE:  Closing pre-existing portal "cfindplu"
>NOTICE:  Closing pre-existing portal "cfindplu"
>[... snip ...]
>
>c... stuffs are CURSORS
>
>it seems that on every commit, the cursor is closed... and re-opened with new
>variables'values 
>
By default, Postgres executes transactions in autocommit mode.
This means that each statement is executed in its own transaction and a 
commit is performed
at the end of the statement, what is much slower than executing all 
statements inside a
begin ... commit block.
To disable the autocommit mode you have to compile the ECPG script with 
the -t option.
I Hope that it helps.

Regards,

Antonio Sergio



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: elog() patch
Next
From: Peter Eisentraut
Date:
Subject: Re: elog() patch