| From: | Antonio Sergio de Mello e Souza <asergioz(at)bol(dot)com(dot)br> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oracle vs PostgreSQL in real life |
| Date: | 2002-03-01 15:14:34 |
| Message-ID: | 3C7F9ADA.9000309@bol.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes wrote:
>On Thu, Feb 28, 2002 at 01:18:29PM -0500, Antonio Sergio de Mello e Souza wrote:
>
>>By default, Postgres executes transactions in autocommit mode.
>>
>That of course is true.
>
>>To disable the autocommit mode you have to compile the ECPG script with
>>the -t option.
>>
>That unfortunately is not. It's just the opposite way. ecpg per default uses
>the Oracle way and issues a BEGIN after each commit automatically. Thus you
>only have to specify COMMIT every now and then to end the transaction. If
>you use "-t" or SET AUTOCOMMIT ON, then you run in the normal PostgreSQL
>environment and get each command inside its own transaction. To manually
>start and end transactions you have to use "-t" resp. EXEC SQL SET AUTOCOMMIT ON
>and then issue a BEGIN.
>
Many thanks for the explanation! Sorry for the wrong advice... :-(
Regards,
Antonio Sergio
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-01 15:15:28 | Re: Database Caching |
| Previous Message | Bruce Momjian | 2002-03-01 15:07:31 | Re: elog() patch |