| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | stefan(at)extum(dot)com, Steve Brett <SBrett(at)e-mis(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: COMMIT in PostgreSQL |
| Date: | 2002-07-19 13:48:50 |
| Message-ID: | 12324.1027086530@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Sat, Jul 20, 2002 at 03:03:02PM +0300, stefan(at)extum(dot)com wrote:
>> thanks a lot all for comments. So in PostgreSQL each query is a
>> transaction ?
> If you want them that way. If you want to combine them into one transaction,
> you use BEGIN.
Right; otherwise you get the sort of behavior that some other databases
call auto-commit.
While we can't change this without breaking huge amounts of client code,
there has been talk of offering a parameter setting that could be
changed to support the SQL-standard behavior (which could be thought of
as auto-BEGIN in Postgres terms: any statement implicitly causes a
BEGIN, and then you stay in that transaction until you explicitly say
COMMIT).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-19 13:53:26 | Re: sequence scan, but indexed tables |
| Previous Message | Oliver Elphick | 2002-07-19 13:47:43 | Re: Looking for types: phone number, email addresses |