From: | Steve Brett <SBrett(at)e-mis(dot)com> |
---|---|
To: | stefan(at)extum(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: COMMIT in PostgreSQL |
Date: | 2002-07-19 11:23:14 |
Message-ID: | C05E7DA1218ED411BF8A00105AC95A8E05C0587C@sv-cntrmail.emis.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
AFAIAA each query sent to the backend is a transaction and is treated as
such unless you explicitly send a BEGIN.
If you send a BEGIN then you can send multiple INSERTS etc and then do a
manual COMMIT.
I've never used Oracle (as the comapny I work for can't afford it !) so I
wouldn't be able to supply you with a comparison.
Steve
> -----Original Message-----
> From: stefan(at)extum(dot)com [mailto:stefan(at)extum(dot)com]
> Sent: 20 July 2002 12:51
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] COMMIT in PostgreSQL
>
>
>
> Hey,
>
> I was running a script which does some INSERTS and UPDATE
> some table. I
> found that there is no need for COMMIT; After each statement
> the TABLE is
> immediately commited. Other session via psql can sees ASAP
> the changes to
> the table. So it seems a bit different than Oracle's COMMIT .
> Can somebody
> explain me why this is so in PostgreSQL ?
>
> Are the modifications done without commit statement ?
>
> PostgreSQL looks really interesting and seems to be good SQL
> compliant.
> stefan
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Liddicott | 2002-07-19 11:24:10 | Re: COMMIT in PostgreSQL |
Previous Message | Jakub Ouhrabka | 2002-07-19 10:00:08 | Regular expression validation |