| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Antonio Sergio de Mello e Souza <asergioz(at)bol(dot)com(dot)br> |
| Cc: | Jean-Paul ARGUDO <jean-paul(dot)argudo(at)idealx(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oracle vs PostgreSQL in real life |
| Date: | 2002-03-01 08:12:41 |
| Message-ID: | 20020301081241.GC17165@feivel.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Michael
--
Michael Meskes
Michael(at)Fam-Meskes(dot)De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christof Petig | 2002-03-01 08:17:03 | Re: Arrays vs separate system catalogs |
| Previous Message | Michael Meskes | 2002-03-01 08:05:07 | Re: Oracle vs PostgreSQL in real life |