| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Denis Perchine <dyp(at)perchine(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS |
| Date: | 2001-01-21 18:34:50 |
| Message-ID: | 12629.980102090@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Denis Perchine <dyp(at)perchine(dot)com> writes:
>> lo_import and lo_export always execute in a transaction, just like any
>> other backend operation. There is no need to force them to be done in
>> a transaction block. If you're not clear about this, perhaps you need
>> to review the difference between transactions and transaction blocks.
> Hmmm... Where can I read about it? At least which source/header?
Try src/backend/access/transam/xact.c. The point is that you need a
transaction block only if you need to combine multiple SQL commands
into a single transaction. A standalone command or function call is
still done inside a transaction.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-01-21 18:39:22 | Re: ODBC gives pq_recvbuf: unexpected EOF on client connection |
| Previous Message | Neil Conway | 2001-01-21 17:49:49 | Re: postgres memory management |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2001-01-21 18:52:30 | Re: [PATCHES] binary operators on integers |
| Previous Message | Bruce Momjian | 2001-01-21 13:56:49 | Re: Fix for defaults in createuser |