Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS
Date
Msg-id 12629.980102090@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [PATCHES] Patch to support transactions with BLOBs for current CVS  (Denis Perchine <dyp@perchine.com>)
List pgsql-hackers
Denis Perchine <dyp@perchine.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

pgsql-hackers by date:

Previous
From: Frank Joerdens
Date:
Subject: Re: beta3 vacuum crash
Next
From: The Hermit Hacker
Date:
Subject: Tangent ... For those that like stats ...